-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
Disable test timeouts in meson check globally #247024
Comments
AFAIK |
It looks like greater minds have already thought of this. cc @alyssais |
There's also manually run nixpkgs/pkgs/development/libraries/folks/default.nix Lines 91 to 95 in da617ec
|
I am running in the same problem, trying to build this #247766, failing 10 times for 10 different timeout errors |
I think the only thing left to do on my PR was to incorporate @jtojnar's documentation suggestion — I can do that soon. I got a bit fed up of so many rounds of review so I put it down for a while. |
#213845 is now in staging. |
Sorry for bumping this, but I just had p11-kit's (0.25.3) checks timeout on my Mac VM with the nixos-24.05 branch. Is this properly implemented yet, or is there something that needs to be configured? |
I'm running into the same issue. Is there currently a workaround? |
@szh |
@Artturin is there a way to apply this globally? I'm getting quite a few timeouts in different packages Edit: to clarify -- without having all meson-dependent packages recompile, I just want to set this for the cache misses. |
Doing this globally is what this issue is about. Without rebuilds is not possible as this changes the inputs to the drv. |
Thanks -- I mistakenly thought it was about changing the defaults and that the toggle already existed |
Tip for those who struggle with this, it appears that the timeouts happen when you
Then you can fix it by running: nix-build /nix/store/ph1h78hg21av397ksi56jz4cxycklrh7-p11-kit-0.25.0.drv (Note the hyphen! Wait for that to complete, and then re-run your original command |
Where is this setting supposed to be set? Should I override an existing package that is failing (p11-kit) and add this attribute? |
Just in case anyone still facing this issue, to me instructions were not clear, but I assumed that the settings described above had to be set in an overlay, so below is my snippet:
|
Issue description
So on my mac with employer-imposed antivirus snakeoil, a build of p11-kit just failed because a test timed out after 30s. Running it a few times with hot caches and with no other builds in the background made it finally pass but that really just shouldn't happen.
We have configurable timeouts for the entire build, so I don't think we need any per-test timeouts. If a test needs a few minutes rather than a few seconds one time, so be it. That shouldn't fail an entire build IMHO.
Question to the community: Should we just disable timeouts in meson checks globally?
meson test --timeout-multiplier 0
should do it according to the documentation but I'm a bit at a loss wheremeson test
is even invoked or else I'd have made a PR. Perhaps meson maintainers know how this works (cc @brandonedens @AndersonTorres).The text was updated successfully, but these errors were encountered: