| 10 Nov 2021 |
 Domen Kožar | * that's fine, that's my miscommunication, I should have posted the plan on the issue | 18:48:32 |
 @grahamc:nixos.org | I put the two machines in to rotation on hydra (named macstadium-x86-*) and we'll pick this up again tomorrow | 18:50:36 |
| Domen Kožar | 
Download 2021-11-10-125128_1030x372_escrotum.png | 18:51:45 |
| Domen Kožar | good :D | 18:52:02 |
| @grahamc:nixos.org | yep, confirmed I have the right key on the machine down stairs for tomorrow 👍️ | 18:52:25 |
| 11 Nov 2021 |
| Domen Kožar | grahamc (he/him): one question, what is the workaround for fixing stuck macos machines, restarting the scheduler? | 10:39:44 |
|  NinjaTrappeur left the room. | 18:24:45 |
 cole-h | 
Download image.png | 21:55:19 |
| cole-h | 👀 | 21:55:21 |
| cole-h | 
Download image.png | 22:31:30 |
| cole-h | 👀 x2 | 22:31:33 |
| 12 Nov 2021 |
| Domen Kožar | nicee | 14:53:51 |
| 14 Nov 2021 |
| Domen Kožar | I've signed us up for https://github.blog/changelog/2021-10-27-pull-request-merge-queue-limited-beta/ waiting list | 16:39:28 |
 tomberek | Should we start using the merge-queue? Potential interactions with incomplete Darwin tests? | 16:50:43 |
 sterni | it would be very useful, but we would have to make ofborg builds (maybe even all of ofborg) irrelevant for progress | 16:52:41 |
| sterni | basically this would allow us to never have eval errors on master which cause quite a bit of friction (happened today incidentally) | 16:53:07 |
|  nixinator joined the room. | 19:42:34 |
 Sandro | In reply to @sternenseemann:systemli.org
it would be very useful, but we would have to make ofborg builds (maybe even all of ofborg) irrelevant for progress yeah, when ofborg is stuck again for darwin it would be really annoying | 19:57:22 |
| sterni | I guess we'll see what kind of configuration options there are for the merge queue | 19:57:55 |
| cole-h | Wouldn't surprise me if they didn't care about external statuses | 20:40:39 |
| 15 Nov 2021 |
| @grahamc:nixos.org | usually on tools like this you can specify specific checks that need to pass | 01:18:46 |
| @grahamc:nixos.org | so we could probably make evaluation mandatory and not require builds | 01:19:07 |
| Sandro | You can already specify mandatory checks in the repository settings | 01:20:54 |
| @grahamc:nixos.org | exactly | 01:21:03 |
| Sandro | Merge trains are when you want to rerun all checks before merging the next PR to not get any stale checks which at some point where green. | 01:21:54 |
| Sandro | If we would do that for every PR we would put a lot of extra stress on ofborg. Also most of our PRs have very little chance for creating side effects of they are merged at the same time. | 01:22:51 |
| Sandro | * If we would do that for every PR we would put a lot of extra stress on ofborg. Also most of our PRs have very little chance for creating side effects if they are merged at the same time. | 01:23:14 |
 Ryan Burns | the merge train is supposed to reduce the amount of evaluation you do, instead of running the eval checks when the PR is open you would run them as a condition of merging | 01:23:38 |
| @grahamc:nixos.org | also the post specifically says it is only looking at required checks | 01:23:42 |
| Sandro | If we account that we have barely thought Darwin builders on ofborg I am not sure if this would be a great idea | 01:23:54 |
