On 2019/10/04 18:22, sven falempin wrote: > on 6.6 snap > > rust entered an infinite loop > > ` (signal: 15, SIGTERM: termination signal) > command did not execute successfully: > "/usr/ports/pobj/rust-1.38.0/rustc-bootstrap-amd64-1.38.0-20190924/bin/cargo" > "build" "--target" "x86_64-unknown-openbsd" "-j" "1" "-v > " "--release" "--frozen" "--features" "" "--manifest-path" > "/usr/ports/pobj/rust-1.38.0/rustc-1.38.0-src/src/rustc/Cargo.toml" > "--message-format" "json" > expected success, got: exit code: 101 > Traceback (most recent call last): > File "/usr/ports/pobj/rust-1.38.0/rustc-1.38.0-src/x.py", line 11, in > <module> > bootstrap.main() > File > "/usr/ports/pobj/rust-1.38.0/rustc-1.38.0-src/src/bootstrap/bootstrap.py", > line 866, in main > bootstrap(help_triggered) > File > "/usr/ports/pobj/rust-1.38.0/rustc-1.38.0-src/src/bootstrap/bootstrap.py", > line 852, in bootstrap > run(args, env=env, verbose=build.verbose) > File > "/usr/ports/pobj/rust-1.38.0/rustc-1.38.0-src/src/bootstrap/bootstrap.py", > line 141, in run > raise RuntimeError(err) > > So if your build take a long time you may want to check that. > > -- > -- > --------------------------------------------------------------------------------------------------------------------- > Knowing is not enough; we must apply. Willing is not enough; we must do >
How long did you wait before sending SIGTERM? It takes getting on for 3 hours on fast i386 builders. could be a lot worse if you are short on RAM and swapping.
