-
Notifications
You must be signed in to change notification settings - Fork 3
CI: fix matrix spec / fix broken bin/benchmark.sh #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
* update rails to 8.0 * Modify the settings in config/environments/test (the setting for action_dispatch.show_exceptions has changed in Rails 7.2). * Change debugger gem 'byebug' to 'debug'
simple_json.gemspec
Outdated
| spec.add_development_dependency 'test-unit-rails' | ||
| spec.add_development_dependency 'mutex_m' | ||
|
|
||
| spec.required_ruby_version = '>= 2.5.0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should update this too.
I remember some new syntax failed in old versions on CI,
since we don't check them any more, maybe we should deprecate old versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
excluded EOL Ruby versions. (following ci changes) 213a821
| Rails.application.config.generators.simple_json false | ||
| ``` | ||
|
|
||
| ## Benchmarks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's update these benchmark results.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, bin/benchmark.sh can not running in RAILS_ENV=production. I plan to fix this issue in a separate PR (and will be update bench result).
ee4cc85 to
213a821
Compare
Some dependencies are updated.
As part of this fix, new (?) warnings are now displayed in “rake test” and other places. However, this issue has not been fixed in this pull request and will be addressed separately.