macOS 12 x86_64 buildbot weirdness
herby.gillot at gmail.com
Sun Apr 10 16:14:11 UTC 2022
Update here: this turned out to have been an issue with Rust itself on
macOS 12 x86_64:
Fixed starting here: https://github.com/macports/macports-ports/pull/14532
On Fri, Apr 8, 2022 at 7:17 PM Ryan Schmidt <ryandesign at macports.org> wrote:
> On Apr 8, 2022, at 10:06, Herby Gwrote:
> > Something weird might be going on with the macOS 12 x86_64 buildbot....
> > Two builds of the same latest Rust fail with completely different errors:
> > 1.
> > 2.
> > Run #1 fails signal 6 (SIGABRT?):
> > rustc exited with signal: 6
> > Did not run successfully: signal: 6
> > error: could not compile `openssl-sys`
> > Run #2 fails due to missing object file (maybe the process got sig'd
> mid-run before it could write out the object file?):
> > error: could not write output to
> No such file or directory
> > error: could not compile `rayon-core` due to previous error
> > Either way, something odd is happening. Maybe the machine should have
> some diagnostics run on memory and CPU.
> I do not think it relates to the issue you mentioned, but there has been
> some network instability today, causing the Apple Silicon buildbot worker
> to disconnect from the master several times and causing some other builders
> not to start builds after being unable to connect to GitHub. I restarted
> any failed builds. The 10.6 i386 worker also experienced one of its
> customary kernel panics during a build, and I rebooted it and the build was
> I restart all build machines periodically to try to avoid problems. Most
> of them (except for 10.6 i386) were restarted yesterday.
> The machine that runs the macOS 12 VM is the same Xserve that runs several
> other VMs, so I do not suspect any hardware problems. Xserves use
> error-correcting memory.
> I'll try another build of rust now.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-dev