Repository navigation
Report where load errors were raised; support Ruby 2.7 and 3.0 - #10
Merged
Merged
Conversation
An error raised outside of a test, such as while a test file loads, ended the run with only `ERROR: <message>`. Print the error's class, the first backtrace line, and a pointer to --debug. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Nothing in the code needs 3.1. On older Rubies Bundler resolves ansi 1.5.0, qed 2.9.2 and ae 1.8.2, the last releases before those gems required 3.1. Add both versions to the CI matrix. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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
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.
Load errors
An error raised outside of a test, such as while a test file loads, ended the run with only
ERROR: <message>: no class, file or line, and no hint that--debugshows the backtrace. That made aFrozenErrorin a project's own library look like a rubytest crash.Test.run!now prints:--debugstill re-raises with the full backtrace. A new section indemo/03_runner_reliability.mdcovers the report.Ruby 2.7 and 3.0
0.9.0 set
required_ruby_versionto>= 3.1, but nothing in the code needs it. On Ruby 2.7 and 3.0 Bundler resolves ansi 1.5.0, qed 2.9.2 and ae 1.8.2, the last releases before those gems required 3.1.With 0.9.0, a project that tests on Ruby older than 3.1 gets rubytest 0.8.1 there, which has no executable, so it has to keep rubytest-cli. On newer Rubies it then has two gems that ship
rubytest, and Bundler warns. Lowering the floor lets such a project drop rubytest-cli.The CI matrix gains 2.7 and 3.0.
Testing
bundle exec rake teston Ruby 3.4.9: 5 demos, 36 steps, 90 assertions, all passing.rubytestexecutable on a test file and on a file that raises while loading, inruby:2.7(2.7.8) andruby:3.0(3.0.7) containers: all passing.🤖 Generated with Claude Code