Skip to content
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

Open
xd009642 opened this issue May 2, 2024 · 3 comments
Open

Test that requires copying .git #348

xd009642 opened this issue May 2, 2024 · 3 comments

Comments

@xd009642
Copy link

xd009642 commented May 2, 2024

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 exotic

For 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

@xd009642
Copy link
Author

xd009642 commented May 2, 2024

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 🤔

@sourcefrog
Copy link
Owner

sourcefrog commented May 2, 2024 via email

@xd009642
Copy link
Author

xd009642 commented May 2, 2024

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 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants