Not sure if this is a bug or a misunderstanding on my part. I seem to be getting inconsistent race-condition like behavior with the following setup: Rakefile: ```ruby multitask :default => [:one, :two] do end task :two => :one do puts "echo 'should not run?'" end task :one do raise end ``` I would expect to never see "should not run?", but I see it intermittently. ``` for i in {1..10}; do rake 2>/dev/null | grep 'should'; done echo 'should not run?' echo 'should not run?' ```
Activity
grzuy commentedon Feb 7, 2018
I was able to reproduce.
Working on a fix.
Don't run tasks if it depends on already invoked but failed task. Fixes
Don't run tasks if it depends on already invoked but failed task. Fixes
grzuy commentedon Feb 23, 2018
The following PR attempts to fix this issue
#252
Merge pull request #252 from grzuy/fix_multitask_failures