| 13 Oct 2021 |
 sterni | I can just restart all aborted ones again | 19:37:54 |
| sterni | * I can just restart all aborted ones again if you link me the evaluation | 19:38:04 |
 toonn | But how would that happen? The commits I pushed touch sphinx. Which caused 1000's of failures before. So I'd expect it to change 1000's of hashes now : s | 19:42:11 |
 Ryan Burns | toonn: you modified the extraPostFetch but didn't change the FOD hash so no hashes changed and nothing will be rebuilt | 19:51:58 |
| toonn | Right... >.< Ok, then I do need the aborted jobs restarted : ) | 19:59:56 |
| toonn | FODs are really a lot less straightforward than I thought they were. | 20:00:39 |
 Vladimír Čunát | Restarted https://hydra.nixos.org/eval/1713061 which you apparently meant. | 20:08:30 |
| Vladimír Čunát | The original motivation of FOD was to avoid rebuild when fetcher is changed, I believe (e.g. URL moves). | 20:09:31 |
| toonn | Thanks. Yeah, they certainly have their uses. It's just that the implications seem obvious and yet they still bite me time and again : ) | 20:10:55 |
| toonn | Excellent, now we wait. (Mr Burns pose.) | 20:13:27 |
| Ryan Burns | lol. I was eagerly watching some of the jobs and they've all gotten stuck in sending inputs now. pikachu face | 20:58:41 |
| toonn | How can you tell? (I'm still not very familiar with interpreting Hydra web interface.) | 21:02:52 |
| Ryan Burns | per job here https://hydra.nixos.org/status or per machine here https://hydra.nixos.org/machines | 21:10:35 |
| toonn | Ah, TIL. That's a much closer eye than I've kept so far : ) | 21:16:24 |
| 14 Oct 2021 |
 K900 | Is anyone looking into the Darwin builder thing? | 11:25:12 |
| K900 | I don't want to build rustc from source :( | 11:25:24 |
 lukegb (he/him) | At the current rate, we're going to have a 21.11 release without x86_64-darwin builds, I'm afraid | 11:31:21 |
 moritz.hedtke | Wouldn't it be possible to run a build manually (with nix-build) on one of the idle ones (and probably disable it in hydra). I could image that would actually be faster. Although I don't know how it would get in the cache then or if there is some other flaw in that | 12:03:57 |
| moritz.hedtke | Investigating what's from is of course way more useful. Also this wouldn't update the channels in the end I assume and if hydra fails before building (which it seems to me) you couldn't even rerun a build there then | 12:07:30 |
| moritz.hedtke | * Investigating what's wrong is of course way more useful. Also this wouldn't update the channels in the end I assume and if hydra fails before building (which it seems to me) you couldn't even rerun a build there then | 12:07:48 |
| toonn | Things like stdenv updates require full rebuilds. That'd be ~28k packages to build manually. Somewhat less because you only need to manually start leaf builds but still. | 12:09:50 |
| lukegb (he/him) | At that point you have a human doing the Hydra scheduler's job, and the time would be better spent fixing the scheduler, imo | 12:10:52 |
| K900 | In reply to @lukegb:zxcvbnm.ninja
At the current rate, we're going to have a 21.11 release without x86_64-darwin builds, I'm afraid Is there a fixed deadline for 21.11? | 12:11:55 |
| toonn | Nov 26th is feature freeze I believe. | 12:12:12 |
| K900 | Yeah but like the actual release | 12:12:21 |
| toonn | If it's not in by then you can't really expect significant changes to still be accepted though. | 12:12:41 |
| K900 | I'm a random nobody so my opinion is irrelevant | 12:12:48 |
| K900 | But I'd rather delay the release than release without cached binaries for the second biggest platform | 12:13:04 |
| toonn | That's not really a great option without a solution in sight though. | 12:14:19 |
| toonn | Have many uncached expressions already made it into the unstable channel? | 12:14:39 |
