-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Flaky test nonce2key #2501
Comments
You are running
The make has to complete before you can run the tests.
|
Of course! To clarify, we build with I'm pretty sure that it's a regression in latest version. Looking at our pipelines at https://gitlab.com/kalilinux/packages/proxmark3/-/pipelines, there has been a fair number of successful builds before, and the test started to be flaky only after I started to build I tried a run without parallel (cf. https://gitlab.com/arnaudr/proxmark3/-/jobs/7815347554/viewer), and I noticed that:
So we end up with two |
Aha, This is a great explanation. Looking at bit in Card_only tests
Card_reader tests
I wonder if we can use |
Would you mind testing this to see if it solves the issue for you? I tried locally and it works for me.
|
I'm trying again with:
In the top-level Makefile, CHECKARGS is documented as being something the caller can use, so better not use it and leave it for the caller |
Did you pull latest ?
running your idea with direct args, works on my machine (wsl / ubuntu). |
Ah no, sorry, I just applied the changes in Direct args as I mentioned in #2501 (comment) also works for me I can open a MR if you want, but otherwise feel free to apply it yourself (to simplify) if you think it's the right change |
Added your suggested fix. |
Thanks! |
Hello,
I just updated the
proxmark3
package that we distribute in Kali Linux to latest version v4.18994, and I observe that a test is flaky, it fails every now and then:Note the command that we run the tests with parallelization enabled (
make -j8)
, so maybe you won't see the issue if you don't run tests the same way.Best,
The text was updated successfully, but these errors were encountered: