-
Notifications
You must be signed in to change notification settings - Fork 54
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 failures for manifest and control tests on Arch Linux #111
Comments
@ximon18 any idea what's happening there? |
I'm not familiar with Arch Linux but an attempt to reproduce the problem in a Docker container failed as those tests pass but a different one fails:
|
That failure looks similar to #75 |
Hi @orhun, Thanks for the link. Ignoring the Can you give more guidance on how to reproduce the issue, as just running It's been a long time since I looked at the Thanks, Ximon |
Sure. Here are the steps to reproduce the behavior:
Alternatively you can use an Arch Linux docker image and use |
Sorry, still unable to reproduce. I tried using the Docker approach, as follows: In one shell session:
Now leave that shell open and in a new shell do:
|
Ah, maybe the Docker approach is not the same as building in a clean chroot. Can you try building with |
First I should check if I actually ran the tests that fail - I'm now thinking I didn't modify the clone so if it has the skip args then the tests would have been skipped - that's what I get for trying to squeeze it in a free moment 🧐 |
Hello!
I'm trying to update
cargo-deb
in Arch Linux repository and I'm getting the following errors duringcargo test
:There isn't much changed between the last version and current version so it is a bit mysterious why the tests are failing now. Maybe something changed in cargo?
I will be skipping the tests as a workaround for now. Let me know if we can do anything about this!
The text was updated successfully, but these errors were encountered: