Gregory Szorc
Gregory Szorc
> I ran it on my M3, so it seems more likely that none of the x86 feature sets were involved at all? Yup. This is closer to a Rust...
I think that providing a public certificate without its signing key should be a fatal error. Thanks for filing the issue!
The 3.13 CI jobs aren't yet fully optimized and already this PR drops Linux builder total time from ~64h to ~43h, or ~67% of baseline. Not bad.
The macOS builds should be fixed. Issue turned out to be a compatibility issue changed in GNU Make 3.82 (macOS ships 3.81). Specifically commit 81f3e4babd128f6740d05b371122762924522fb6 (because I bisected it). `define`...
Ok. CI came back clean. macOS CI total time drops from 10:27 to 8:49. 529/627=84% of baseline. Not the percentage savings as Linux. And 3.13 is still on the table...
Actually, the time savings may be 5x slower decompression doesn't translate to a meaningful wall time difference?
For the manually created zstd variant, did you create a new tar or was the inner tar archive reused? (Ordering of files within the tar can affect filesystem performance. PBS...
I pushed a pile of crate updates a few hours ago and believe this issue has been resolved.
I'd just ignore this since it doesn't just work.
Let's just not build stuff in CI unless we release it. If people insist on maintaining build system support for an esoteric config that we don't release, I'm receptive to...