| 16 May 2025 |
emily | though that was in part just because it was pre-branchoff | 22:13:54 |
Tristan Ross | Oh, yeah I forgot about that PR lol | 22:14:18 |
Randy Eckenrode | I have run into some other failures, but I don’t know if they’re related. catch2 (transitive dependency of mpv) fails to build. Another one did as well, but I don}t recall what it was off hand. | 22:58:51 |
Tristan Ross | I think it's generally okay if there's some failures, it's just critical things. And we can fix it when we see it. | 23:18:46 |
emily | triage bandwidth is an issue, if it holds up security fixes in the -next cycle because a ton of stuff is broken on Darwin | 23:25:04 |
emily | I assume we're not looking at LLVM 19 levels of breakage though | 23:25:12 |
emily | GCC 15 bump should be about due too… | 23:25:19 |
Tristan Ross | Yeah, this is one of the reason why I think these sorts of things should be done early after branch off since it gives us the maximum amount of time to fix issues. | 23:45:50 |
emily | well, for -next that doesn't help so much, since we can only merge if at least all channel blockers are working, and there's always security fixes in the pipeline | 23:46:27 |
Tristan Ross | Maybe in the next staging cycle or this one we could do it? | 23:46:33 |
emily | beyond -next timing earlier in the cycle is best of course | 23:46:35 |
emily | but the less testing that's done up-front the more likely a big bump is to block the cycle and the more triage bandwidth during the cycle is required ultimately | 23:46:57 |
Tristan Ross | Yeah, find and fix what we can mostly in the pre-commit rather than merging. | 23:47:34 |
| 17 May 2025 |
Tristan Ross | Cool, rust builds with LLVM 20 just fine | 00:48:36 |
emily | that's what they build with upstream | 01:10:05 |