Change the log level for the fork interception #394

Activity

1. st0012 commented on Nov 30, 2021

   

   st0012

   on Nov 30, 2021

   Member

   More actions

   If you're talking about these messages: "Detaching after fork ...." and "Attaching after process ...", I think they can be downgraded to debug in the future. But at the moment, the forking mechanism isn't completely stable and can cause issues like #336. Having this message can help users be aware of process forking and identify/report the problem.
2. ko1 commented on Dec 2, 2021

   

   ko1

   on Dec 2, 2021

   Collaborator

   More actions

   Does it hurts your test or your favorite?
3. JunichiIto commented on Dec 31, 2021

   

   JunichiIto

   on Dec 31, 2021

   Contributor

   More actions

   When I run RSpec against Rails 7 application, I see this warning. It's noisy a little to read the result of tests.

   $ bundle exec rspec -f progress
   ...................................................................DEBUGGER: Attaching after process 69034 fork to child process 69055
   ...
   
   Finished in 3.26 seconds (files took 1.79 seconds to load)
   70 examples, 0 failures
   

   In addition, this warning is displayed in red when I run tests within RubyMine's terminal. I sometimes misunderstand that something is wrong with my application.

   

   I'd be glad if it is suppressed by default.

   👍React with 👍2Reacted by Sean Björnsson and Andrei Erdoss
4. ko1 commented on Dec 2, 2022

   

   ko1

   on Dec 2, 2022

   Collaborator

   More actions

   #823 makes it INFO level.
5. ko1

   closed this as completedon Dec 2, 2022