| 13 Sep 2021 |
 Vladimír Čunát | Though perhaps that was helped by several thousands of new quick failures :-/ | 10:16:57 |
 lukegb (he/him) | Yeah :/ | 10:33:14 |
| lukegb (he/him) | 
Download Screenshot_20210913-113558.png | 10:36:28 |
 hexa | jonringer: can you merge master into staging-next, some azure-cli conflicts | 13:31:13 |
| hexa | * jonringer: can you merge master into staging-next? some azure-cli conflicts | 13:31:19 |
 jonringer | yea | 14:59:00 |
| jonringer | Done | 15:19:47 |
 trofi | https://hydra.nixos.org/build/152590415 evil build refuses to retry even after I fixed an URL (shich makes sense as hash did not change): https://github.com/NixOS/nixpkgs/pull/137378. What does it take to get "job restart" privileges? I would try a few on trunk and staging-next :) | 20:21:56 |
| Vladimír Čunát | Well, I restarted it now. (I can't give privileges anyway.) | 20:53:44 |
| Vladimír Čunát | Bad fixed-output derivations are a bit problematic sometimes. | 20:54:15 |
| trofi | Thank you! | 21:19:45 |
| 14 Sep 2021 |
| trofi | Another suspicious failed build is llvm-10.0.1: https://hydra.nixos.org/build/151128054. Substitutions are available for me, but hydra believes it's a failing derivation. | 07:22:40 |
| Vladimír Čunát | Yes, that happens if it failed and then it got restarted as part of another build. The old build will remain failed, but binaries got uploaded and even log gets rewritten on retries. | 07:29:10 |
| Vladimír Čunát | * Yes, that happens if it failed and then it got restarted (manually) as part of another build. The old build will remain failed, but binaries got uploaded and even log gets rewritten on retries. | 07:29:24 |
| lukegb (he/him) | Down to 8000 x86_64-darwin and 11045 aarch64-darwin builds | 09:01:32 |
| lukegb (he/him) | In reply to @lukegb:zxcvbnm.ninja
Down to 8000 x86_64-darwin and 11045 aarch64-darwin builds No, Element's default font's ligature, not "multiplied by 86", x86 | 09:02:13 |
| 15 Sep 2021 |
| lukegb (he/him) | https://p.lukegb.com/raw/RemotelyWiredSkylark.png we're close | 00:09:11 |
 asbachb | In reply to @lukegb:zxcvbnm.ninja
https://p.lukegb.com/raw/RemotelyWiredSkylark.png we're close I'm unsure what this graph shows :> | 03:40:53 |
| asbachb | Open builds to be executed?! | 03:41:10 |
| Vladimír Čunát | Builds in staging-next that haven't been finished. | 06:01:59 |
| lukegb (he/him) | There was a pile of aarch64-darwin builds added yesterday by the last eval | 06:11:20 |
| Vladimír Čunát | Merged stagings. To 21.05 half a day ago and to master now. | 06:36:43 |
| Vladimír Čunát | * I merged stagings. To 21.05 half a day ago and to master now. | 06:37:06 |
| Vladimír Čunát | * I merged staging-next branches. To 21.05 half a day ago and to master now. | 06:38:16 |
| lukegb (he/him) | Sorry for causing a late Darwin stdenv rebuild, heh | 06:38:45 |
| lukegb (he/him) | I hope the merge worked correctly after our merging mishaps | 06:39:17 |
| Vladimír Čunát | I didn't check. Were there some reverted merges? | 06:40:37 |
| lukegb (he/him) | Yeah, but I think we ended up in a good state: mostly it was down merges so we should be alright. We had some shenanigans between staging, python-unstable and staging-next | 06:41:41 |
| trofi | What would be a rule of thumb for a change to be considered big WRT caused rebuilds to go to staging instead of master branch? I was surprised to see 2.5K being not too big: https://github.com/NixOS/nixpkgs/pull/137973 | 08:40:45 |
| lukegb (he/him) | It doesn't get moved automatically | 08:43:12 |
