| 12 Sep 2021 |
 lukegb (he/him) | https://p.lukegb.com/raw/ViolentlySteadyHound.png heh | 13:36:23 |
 Sandro | that is not going anywhere | 13:41:11 |
| lukegb (he/him) | The linux builds are fine | 13:41:20 |
| lukegb (he/him) | (the queue runner seems to believe that there are 4 jobs scheduled on each of the m1 macs, although they don't show up on the machine status page) | 13:57:45 |
| Sandro | I think we should merge staging-next at this point. Most of the python regressions are known or can be easily fixed after the merge. | 18:50:12 |
 hexa | there are no substantial python regressions | 18:53:02 |
| Sandro | at this point there is more and more stuff on staging-next that is needed on master. One example is rust 1.54. Crates start to use newer rust features and compilation falls apart. | 18:53:05 |
 Vladimír Čunát | Linux builds will probably catch up within several hours from now. | 18:57:22 |
| Vladimír Čunát | So far the regression numbers+list look OK-ish to me. (on Linux... on Darwin there isn't much yet, really) | 18:59:36 |
| Sandro | Based on the darwin progress the last days we can't really wait for it | 19:00:31 |
| Sandro | you take the queued numbers from https://hydra.nixos.org/queue-summary ? or is there something fancier? | 19:01:52 |
| Vladimír Čunát | Including last-minute stdenv rebuilds is problematic. Especially the early bootstrapping needs lots of serial time, too. | 19:02:33 |
| Vladimír Čunát | https://hydra.nixos.org/queue-runner-status is another nice URL (and there's no link or button to it AFAIK) | 19:05:07 |
| Vladimír Čunát | Not "fancier" though :-) | 19:05:31 |
| Sandro | hmmm | 19:06:24 |
| Sandro | so you think we can merge it later today or tomorrow? | 19:06:44 |
| Vladimír Čunát | I'm not sure. There are down-sides, e.g. x86_64-darwin in OfBorg will become unusable for some time. | 19:09:15 |
| hexa | 
Download image.png | 19:11:15 |
| hexa | In reply to @vcunat:matrix.org
https://hydra.nixos.org/queue-runner-status is another nice URL (and there's no link or button to it AFAIK) ^ | 19:11:18 |
| Sandro | In reply to @lukegb:zxcvbnm.ninja
https://p.lukegb.com/raw/ViolentlySteadyHound.png heh based on this darwin will take a really long time | 19:11:43 |
| Vladimír Čunát | In reply to @hexa:lossy.network
sent an image. Where is that? | 19:12:14 |
| hexa | frontpage | 19:12:25 |
| Vladimír Čunát | That graph showed early time when stdenv rebuild was starting. But nevertheless, full rebuild certainly takes days on x86_64-darwin, even if there's no other work. | 19:23:41 |
| Vladimír Čunát | * That graph showed early time when stdenv rebuild was starting. But nevertheless, full rebuild certainly takes days on x86_64-darwin, even if there was no other work. | 19:23:48 |
| Sandro | linux does not take days, right? | 19:49:00 |
| Vladimír Čunát | I'd think it would be two days at least. | 19:49:36 |
| Vladimír Čunát | (if there was no other work) | 19:49:48 |
| Sandro | thats pretty long... | 19:50:03 |
| Vladimír Čunát | It's lots of work. It would probably be a bit better if more servers were paid for, though I can't be sure if some (other) bottleneck could appear anyway. | 20:08:48 |
| lukegb (he/him) | In reply to @vcunat:matrix.org
It's lots of work. It would probably be a bit better if more servers were paid for, though I can't be sure if some (other) bottleneck could appear anyway. It's definitely not just that, though. The aarch64-darwin staging-next queue hasn't reduced in size ~for the last day or so, and the only other builds in it are nixpkgs-unstable-aarch64-darwin, which shouldn't be stealing all the cycles | 21:59:50 |
