Fix 'travis monitor' on Linux#770
Merged
BanzaiMan merged 1 commit intotravis-ci:masterfrom Oct 8, 2020
Merged
Conversation
Just loading notification.rb causes the Dummy class constructor to fail, because of non-existing path in Asset. This seems to be caused by some recent changes in asset.rb, but the proper fix is to not rely on non-existing path. Before this fix the error message is: ``` Traceback (most recent call last): 18: from /home/user/bin/travis:23:in `<main>' 17: from /home/user/bin/travis:23:in `load' 16: from /home/user/.gem/ruby/gems/travis-1.10.0/bin/travis:18:in `<top (required)>' 15: from /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/cli.rb:62:in `run' 14: from /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/cli.rb:69:in `command' 13: from /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/cli.rb:69:in `const_get' 12: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require' 11: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require' 10: from /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/cli/monitor.rb:2:in `<top (required)>' 9: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require' 8: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require' 7: from /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/tools/notification.rb:6:in `<top (required)>' 6: from /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/tools/notification.rb:7:in `<module:Travis>' 5: from /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/tools/notification.rb:8:in `<module:Tools>' 4: from /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/tools/notification.rb:26:in `<module:Notification>' 3: from /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/tools/notification.rb:27:in `<class:Dummy>' 2: from /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/tools/assets.rb:9:in `asset_path' 1: from /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/tools/assets.rb:9:in `tap' /home/user/.gem/ruby/gems/travis-1.10.0/lib/travis/tools/assets.rb:10:in `block in asset_path': Travis CI.app/Contents/MacOS/Travis CI (Travis::Client::AssetNotFound) ```
Contributor
|
Thanks for the PR! |
|
I see a version history set as |
Contributor
|
Because 1.10.1 has not been released. https://rubygems.org/gems/travis/versions |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Just loading notification.rb causes the Dummy class constructor to fail, because of non-existing path in Asset. This seems to be caused by some recent changes in asset.rb, but the proper fix is to not rely on non-existing path.
Before this fix the error message is: