-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test that requires copying .git
#348
Comments
Actually, despite working around that cargo-mutants doesn't run on tarpaulin... Dose cargo-mutants make use of unix signals if so that might break things for me 🤔 |
The easiest workaround for the git issue is probably `--in-place`, or
copying it yourself then using that.
The main thing cargo-mutants uses signals for is to kill hung tests, and to
stop them if it's interrupted itself.
Can you describe how to reproduce the problem with Tarpaulin?
…On Thu, May 2, 2024, 4:48 AM xd009642 ***@***.***> wrote:
Actually, despite working around that cargo-mutants doesn't run on
tarpaulin <https://github.com/xd009642/tarpaulin>... Dose cargo-mutants
make use of unix signals if so that might break things for me 🤔
—
Reply to this email directly, view it on GitHub
<#348 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACUR42PH2XB22XHU5F45Y3ZAIRXNAVCNFSM6AAAAABHDPTACKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJQGMYDGNZYGM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
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
|
So I'm in a definitely very unique situation where I have a test that requires the repos
.git
folder so I need something a bit more aggressive than the--gitignore true
flag. I'm currently using--in-place
in a separate clone of the project to avoid accidentally breaking something so there is an easy way round this if this is too exoticFor the interested this is because I interact with the coveralls API and part of that API you provide some git and github metadata so I test against the repos own metadata to make sure I'm filling out the API fields correctly
The text was updated successfully, but these errors were encountered: