| 17 Sep 2021 |
lukegb (he/him) | mac2-guest might be wedged again: https://hydra.nixos.org/build/153432095 | 19:25:18 |
sterni | next evaluations should fix the tarball jobs, but we should keep an eye on them since they timed out a few times which worries me | 20:30:03 |
| 21 Sep 2021 |
toonn | I was looking for a good Hydra evaluation to rebase a PR on to target staging but the listed evaluations are all pretty old. Should I using nixpkgs:staging-next instead? | 08:16:18 |
Vladimír Čunát | Depends what you want from the commit. | 08:17:24 |
Vladimír Čunát | staging-small jobset gives some basic binaries (and tests a few packages) | 08:17:53 |
Vladimír Čunát | staging-next has full rebuilds, and at this moment is in quite a good state (not too many build regressions, rebuilds finished). | 08:18:45 |
| 26 Sep 2021 |
lukegb (he/him) | a lot of the x86_64-darwin builders appear to be working on builds that haven't completed in 8 days, and some of them have been "sending inputs" for 7h+ | 16:01:01 |
| 28 Sep 2021 |
lukegb (he/him) | https://cloudblogs.microsoft.com/opensource/2021/09/28/announcing-azure-credits-for-open-source-projects/ even more hydra builders? :P | 21:16:40 |
| 29 Sep 2021 |
sterni | what do you think about a label for recurring PRs (staging-next, haskell-updates, ...)? These can be a bit of a pain to find if you want to use the PR view | 11:58:47 |
sterni | opening the branch and clicking on the PR kinda works, but it hasn't displayed properly for me before | 11:59:09 |
hexa | we kinda set up #staging:nixos.org to mention the latest runs, though I admit that did not always work 🙂 | 12:00:51 |
lukegb (he/him) | That would be neat; I started explicitly naming it "staging-next $DATE" to make it more searchable for myself, but a label would be great | 12:00:54 |
sterni | the problem is also that github doesn't rank search results by relevance so prs with staging next in their title get drowned out for some reason | 12:02:26 |
lukegb (he/him) | Ah yeah, I cheat by filtering by author:lukegb when I know when I opened it :p | 12:04:08 |
lukegb (he/him) | Iirc there's actually a search term for the source and destination branches | 12:04:31 |
sterni | yeah that's what I do for haskell-updates, but it requires extra knowledge of course | 12:04:45 |
sterni | ahh right | 12:04:49 |
sterni | you want head:staging-next | 12:05:56 |
sterni | 0469fb3d (x86_64-darwin) seems stuck :| | 12:59:32 |
Alyssa Ross | sternenseemann: I have https://github.com/NixOS/nixpkgs/compare/master...staging-next bookmarked for finding the PR, and it seems to work every time | 13:46:17 |
Alyssa Ross | but a label sounds like a great idea, especially for finding previous PRs | 13:46:37 |
hexa | In reply to @sternenseemann:systemli.org 0469fb3d (x86_64-darwin) seems stuck :| what else is new? 🙂 | 14:14:13 |
Vladimír Čunát | And the label... how will people utilize it to make life easier? Is typing label:foo harder than typing head:staging-next? (our labels tend to have quite elaborate names) | 14:24:26 |
Vladimír Čunát | * And the label... how will people utilize it to make life easier? Is typing label:foo easier than typing head:staging-next? (our labels tend to have quite elaborate names) | 14:24:46 |
Vladimír Čunát | * And the label... how will people utilize it to make life easier? Is typing label:foo really easier than typing head:staging-next? (our labels tend to have quite elaborate names) | 14:24:50 |
Alyssa Ross | a label is something you can click from a PR you're already looking at -- I didn't know you could do head:staging-next | 14:25:22 |
Alyssa Ross | but we could also just include a link to that in the template or something | 14:25:32 |
Vladimír Čunát | I've been trying to mention the next staging-next PR in the previous one. (some people did it the other way, too) | 14:26:50 |
Vladimír Čunát | A working link (whatever we prefer) could be added at least to the docs. Some recent staging-next PRs even have the link at the top, some only copied (docs) without any link :-) | 14:29:48 |
Rick (Mindavi) | In reply to @qyliss:fairydust.space but we could also just include a link to that in the template or something I think adding a link to search head:staging-next would be a good way to do it | 15:14:33 |