chromium build cycling on Hydra #49442
Comments
|
Looking at job lists (e.g. trunk), it always started exactly on 69 -> 70 bump, both on master and 18.09, so we could most likely avoid the problem temporarily by reverting that bump. |
|
I now at least manually cancelled most of the jobs, so there aren't too many versions tried at once. |
|
That post seems windows-specific. It's over a year old, and at least at that time I had no such issues when building chromium via nix(os) in background (I haven't tried now yet). |
|
Hm, so it started failing before switching to clang, which is simultaneously good and bad news ;-) Sorry, that I didn't catch this failure. I have now starred Unfortunately, the aborted jobs don't seem to have log files available. Do you have any hint as to what caused it to abort? @vcunat I'll keep an eye on https://hydra.nixos.org/build/83226757/nixlog/140/tail |
|
No, I found no relevant logs. |
|
|
|
OK, that build you linked succeeded 🎉 I hope that's it, but we'll see. |
|
The build succeeded but the tests are now failing due to changes in the sandbox outputs. @bendlas Could you have a look at them? Here is a screenshot of the VM test that fails:
The logs from 18.09 before the recent systemd bump: https://gist.github.com/andir/2b64a68bb0bf953ebe02102aca358b44 & hydra log for comparison https://nix-cache.s3.amazonaws.com/log/adaq71i6yc400pm392d4hc04xwl9ick1-vm-test-run-chromium-stable.drv hydra build: https://hydra.nixos.org/build/83250711 |
|
Related problem I see now: NixOS/hydra#591 (comment) |
|
I've pushed 89ede97 in a desperate attempt to fix timeout issues. |
/cc #49442. It should decrease the waste of resources due to abortions.
As reported by @andir, the regular expressions that match the sandbox output are no longer matching in the recent Chromium bump as of bb03fbc. Instead of a boolean field that determines whether namespace sandboxes are on, the namespace sandbox is now an enum within "Layer 1 Sandbox". I've modified the regular expressions accordingly and also ran the test for the stable branch, which now succeeds. Signed-off-by: aszlig <aszlig@nix.build> Issue: #49442 Cc: @bendlas, @andir (cherry picked from commit 73cdd5a)
As reported by @andir, the regular expressions that match the sandbox output are no longer matching in the recent Chromium bump as of bb03fbc. Instead of a boolean field that determines whether namespace sandboxes are on, the namespace sandbox is now an enum within "Layer 1 Sandbox". I've modified the regular expressions accordingly and also ran the test for the stable branch, which now succeeds. Signed-off-by: aszlig <aszlig@nix.build> Issue: #49442 Cc: @bendlas, @andir
|
Here's an out-of-space error on packet-t2-4, but those aren't that often. |
|
We now had multiple successes of the test and chromium itself, on both branches. Thanks everyone! |
and others
The chromium builds are now repeatedly "aborted" on Hydra.nixos.org, and it isn't even clear why. The result is huge waste of resources, and blocked channel due to never finishing.
Examples:
I see it happening on two different machines. @edolstra: any idea how to get some logs from the abortions? Otherwise I can't see how to deal with it. Also /cc @grahamc (Packet machines).
My first guess would be that it exhausts some resource, e.g.
/tmp/space.The text was updated successfully, but these errors were encountered: