1) IsCovered accepts input from the Windows file system by normalizing slashes.
2) The report must be shown even if there was an error, otherwise the user cannot know what's wrong.
3) Windows runs into timeouts for unknown reasons. The executor runs without cancel for now until it's clear why Windows has a problem here.
Types of changes
[X] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
Proposed changes
1) IsCovered accepts input from the Windows file system by normalizing slashes. 2) The report must be shown even if there was an error, otherwise the user cannot know what's wrong. 3) Windows runs into timeouts for unknown reasons. The executor runs without cancel for now until it's clear why Windows has a problem here.
Types of changes
Checklist
make all
)Further comments
With one worker only, it run quite fast:
With standard settings it takes much longer and some mutants survive:
Why?
The changed will break one test: I cannot find out why "it recognizes CONDITIONAL_BOUNDARY with GTR" in engine_test.go fails.