You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the rake runner build step in TeamCity we get an issue when parallel_drop[XXX] it calls the executing command via $0. which is the rakerunner. (this only broke after upgrading to Ruby 3.1)
$0 seems to have worked for everyone so far, so I'm hesitant to change it.
Afaik simplest solution would be to add some kind of PARALLEL_RAKE_RUNNER= env var.
Alternative could be to find something similar to $0 but idk if that exists.
Yes I was also thinking of an ENV switch. I can try prototype something over the holidays and open a pull. I understand the reluctance to change from the $0. I was however curious if parallel would work with anything else than rake?
Thanks for getting back to me and thanks for all the hard work over the years on your repos.
When using the rake runner build step in TeamCity we get an issue when
parallel_drop[XXX]
it calls the executing command via $0. which is the rakerunner. (this only broke after upgrading to Ruby 3.1)parallel_tests/lib/parallel_tests/tasks.rb
Line 160 in fc09051
The fix is to not use the rake runner and use a custom script in the build step, however I was curious if $0 should be used at all.
The text was updated successfully, but these errors were encountered: