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.
Until now, when I delved into the code, I always got confused with the channels, jobsets, and the architectures. It always annoyed me how these terms are intermingled, and why e.g darwin doesn't use the unstable jobset, and what is the difference between it and
master
...I also felt as if hydra-check doesn't help me a lot to hide all of these details, because whenever I wanted to check whether a package already fails on Darwin on hydra, I had to open the README, which up until now didn't include a single darwin architecture example, and try out the different jobsets...
Anyway, with the changes here, hopefully users won't be frustrated as I was :). The first 2 commits change only the docs and the
--channel
help text - they make the distinction between channels and jobset a bit clearer. The last commit makes the--arch
choice affect the default jobset chosen, where darwin is taken into special consideration.