Skip to content
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

nixos/xsslock: wait until pgrep xlock succeeds #40810

Merged
merged 1 commit into from May 20, 2018

Conversation

Ma27
Copy link
Member

@Ma27 Ma27 commented May 20, 2018

Motivation for this change

Please refer to the conversation in the original PR (#40619) for further
reference: #40619 (comment)

It takes some time after the standby to trigger the locker which might
break the test on Hydra.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

Please refer to the conversation in the original PR (NixOS#40619) for further
reference: NixOS#40619 (comment)

It takes some time after the standby to trigger the locker which might
break the test on Hydra.
@Ma27
Copy link
Member Author

Ma27 commented May 20, 2018

/cc @xeji hopefully this fixes the broken test %)

@xeji xeji merged commit 4db2d4d into NixOS:master May 20, 2018
@Ma27 Ma27 deleted the fix-xsslock-test branch May 21, 2018 06:45
@Ma27
Copy link
Member Author

Ma27 commented May 21, 2018

the i686 build passes now on Hydra. The x86 build (https://hydra.nixos.org/build/74478142) remains broken. If I understand the log correctly it times out while waiting for /dev/vda. Therefore we can be fairly sure that this is a simple Hydra issue. I’d wait and observe how the tests behave during the next builds and then we can decide whether or not to consider this fixed :)

@xeji
Copy link
Contributor

xeji commented May 21, 2018

The x86 failure is unrelated. I've seen these several times before. Looks like a sporadic issue on the hydra builder - the VM doesn't find its primary disk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants