| 11 Sep 2021 |
 sterni | if it's already merged into staging, I'd just wait, less hassle | 20:40:59 |
 asbachb | It's a little bit annoying as building myself takes several hours due to the dependencies. | 20:41:27 |
| sterni | sure, but the staging(-next) workflow ensures that staging (and to an extent) staging-next are the only branches where this happens | 20:42:49 |
 trofi | what is the rough criteria to merge staging-next into master? zero build failures on both? or when staging-next is stirctly better? | 21:09:42 |
| asbachb | I wonder if it makes sense to provide the binaries for staging next somehow. Maybe this would also encourage more people to help fixing. | 21:14:42 |
| asbachb | But testing a fix maybe waiting several hour for the dependencies to build it quite annoying. | 21:14:57 |
| sterni | everything built on hydra is available via the binary cache, so if something has been built, it's substituted | 21:15:40 |
| sterni | staging-next is built on hydra, staging not | 21:16:30 |
| sterni | * staging-next is built on hydra, staging not atm | 21:16:36 |
| asbachb | I see. | 21:16:40 |
| asbachb | Sorry. | 21:18:02 |
| 12 Sep 2021 |
 Vladimír Čunát | staging as well but only in a very small jobset: https://hydra.nixos.org/jobset/nixos/staging-small | 08:22:49 |
 Sandro | What is blocking the current cycle? Darwin only? | 08:30:41 |
| Vladimír Čunát | *-linux has 20k unfinished jobs. | 08:32:02 |
| Vladimír Čunát | and maybe a couple hundred regressions? | 08:32:34 |
| Sandro | We need to do a hands on on how to read hydra... | 08:32:35 |
| Vladimír Čunát | https://hydra.nixos.org/eval/1703680?filter=linux&compare=trunk | 08:32:53 |
| Vladimír Čunát | On a quick glance there's lots of python stuff that's regressed. | 08:33:59 |
| Sandro | Great! That view is helpful. Not sure how to get there. Maybe we should always post such links to make it easier for people to help in the effort. | 08:35:04 |
| Sandro | I might be able to look at some of those things later | 08:35:21 |
| Vladimír Čunát | Well, you get the first part by clicking on the latest eval. Then I ususally edit to add ?compare=trunk but on the right there's a blue "compare to" button. (and the filtering has an easy box) | 08:38:42 |
| Vladimír Čunát | * Well, you get the first part by clicking on the latest eval (when viewing the jobset). Then I ususally edit to add ?compare=trunk but on the right there's a blue "compare to" button. (and the filtering has an easy box) | 08:39:02 |
| Vladimír Čunát | BTW, compare= also accepts number of any particular evaluation. | 08:39:24 |
| Sandro | Thanks | 09:10:16 |
 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 |
