macOS 12 x86_64 buildbot weirdness

Chris Jones jonesc at hep.phy.cam.ac.uk
Fri Apr 8 15:19:34 UTC 2022


The errors below to me more suggest issues with free disk space than memory or cpu. But yes it seems the build should be checked.

Chris

> On 8 Apr 2022, at 4:06 pm, Herby G <herby.gillot at gmail.com> wrote:
> 
> 
> Hello,
> 
> 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. https://build.macports.org/builders/ports-12_x86_64-builder/builds/26275/steps/install-port/logs/stdio
> 2. https://build.macports.org/builders/ports-12_x86_64-builder/builds/26314/steps/install-port/logs/stdio
> 
> 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 /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_lang_rust/rust/work/rustc-1.60.0-src/build/x86_64-apple-darwin/stage2-tools/x86_64-apple-darwin/release/deps/rayon_core-9641c1e2ac352716.rayon_core.ce832f4d-cgu.2.rcgu.o: 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20220408/d52d5597/attachment.htm>


More information about the macports-dev mailing list