chromium: See if Hydra obeys a 24h meta.timeout #39570
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Synthetica9
pushed a commit
to Synthetica9/nixpkgs
that referenced
this pull request
May 3, 2018
This reverts commit 1d06254. We now get a build and maybe have a workaround NixOS#39570; /cc NixOS#39476.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
Fixes #39476. Well, works around it at least.
It appears that Hydra has some support for setting timeout values. Experiments show that meta.timeout does carry over to timeout in builds column, but it's a bit unclear whether that actually carries through anywhere (yet?)
Discussion on #nixos-dev culminated in "let's try it!"