Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Motivation for this change
I already did that once in 359bf7f.
Nix has its own timeout settings, so there is no risk in running
I already did that once in 359bf7f. That change mysteriously got lost somehow (presumably in some merge commit). Nix has its own timeout settings, so there is no risk in running forever. At the same time, some tests can exceed the default timeout (30minutes per file for --long tests) when run on many weak cores (like the aarch64 community builder or some hydra builders).