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
So tarpaulin tests instrument binaries with breakpoints and do coverage which involves intercepting signals going to the process and handling them in code. There's a possibility I'm intercepting the cargo mutants kill signal and then failing the test because it's got an unexpected termination signal 🤔
Reproducing is pretty simple, it's just cloning tarpaulin and running cargo mutants on it
git clone --depth 1 https://github.com/xd009642/tarpaulin
cd tarpaulin
cargo mutants --in-place
@xd009642 I can reproduce this; I haven't looked into why yet. I see a bunch of test failures during the baseline test. Since it isn't timing out, it should not be getting signaled. I guess something else about the environment where cargo-mutants runs it might be causing a problem?
I will look into it some more when I get a chance, but if you want to investigate then a good place to start would be to get the command that it runs from mutants.out/debug.log and run that yourself, and see if it causes the same failure.
Originally posted by @xd009642 in #348 (comment)
The text was updated successfully, but these errors were encountered: