mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
5e9a3e1292
Currently the log returned by running ActiveJob tests is filled with: > DEPRECATION WARNING: Returning `false` in a callback will not implicitly halt a callback chain in the next release of Rails. To explicitly halt a callback chain, please use `throw :abort` instead. For instance, see https://travis-ci.org/rails/rails/builds/77978273 This happens because some setup and teardown methods [like these one](https://github.com/rails/rails/blob/master/activejob/test/cases/async_job_test.rb#L10-L17) invoke other methods like `perform_asynchronously!` that can return `false`, but not with the intention of halting the process if they do. In my opinion, these deprecation warnings can be silenced to have the log result cleaner (especially when browsing for errors). |
||
|---|---|---|
| .. | ||
| adapters | ||
| cases | ||
| integration | ||
| jobs | ||
| models | ||
| support | ||
| helper.rb | ||