Re: note to builder (rust)
On 2019/10/08 08:30, sven falempin wrote: > I am not used at compilation looping on flseep '-_- hit H in top(1) to see the other threads.
Re: note to builder (rust)
On Mon, Oct 7, 2019 at 6:54 PM Stuart Henderson wrote: > > On 2019/10/07 14:05, sven falempin wrote: > > On Mon, Oct 7, 2019 at 8:05 AM Stuart Henderson > > wrote: > > > > > > On 2019/10/07 07:46, sven falempin wrote: > > > > On Fri, Oct 4, 2019 at 6:30 PM Stuart Henderson > > > > wrote: > > > > > > > > > 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 > > > > > > > > > > > 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. > > > > > > > > > Hours, 16gb Ram, 64 bit multi core , process was calling fsleep. > > > > Consuming like 16% of one of the 8 cores. ( amd ) > > > > > > There's not enough information to pinpoint anything. All I can say is that > > > rust does build reliably in bulk builds on several architectures .. > > > > > > > # uname -a > > OpenBSD current.home 6.6 GENERIC#320 amd64 > > > > I will test the MP kernel > > > > PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND > > 9521 root 100 231M 301M run fsleep1:01 35.16% rustc > > Don't build ports as root! It is not needed - an unnecessary big risk. > > > It takes ages to build ( AMD Athlon(tm) 5350 APU with Radeon(tm) R3, > > 2046.39 MHz, 16-00-01 ) > > That particular process (35% cpu use, 1 minute cpu time) hasn't been > running for long has it. If it was really stuck I'd expect a much higher > TIME column. > > Rust is a massive resource drain, it takes me hours to build on a 3.8GHz > xeon. I would strongly recommend using the packages unless you have > a lot of patience. > I just build a few package of my own and doxygen depends uppon, i pkg_add-ed it, the above top was me trying again. It took more than 8 hours to build rust (after activating the other cores ) this is crazy ! : I am not used at compilation looping on flseep '-_- Create /usr/ports/packages/amd64/all/rust-1.38.0.tgz Creating package rust-1.38.0 User _pkgfetch couldn't create temp file as /tmp/session.XX: Permission denied Sorry for the noise, nevertheless it is good to know, that one may want to simply 'pkg_add doxygen' before starting a build -- -- - Knowing is not enough; we must apply. Willing is not enough; we must do
Re: note to builder (rust)
On 2019/10/07 14:05, sven falempin wrote: > On Mon, Oct 7, 2019 at 8:05 AM Stuart Henderson wrote: > > > > On 2019/10/07 07:46, sven falempin wrote: > > > On Fri, Oct 4, 2019 at 6:30 PM Stuart Henderson > > > wrote: > > > > > > > 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 > > > > > > > > > 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. > > > > > > > Hours, 16gb Ram, 64 bit multi core , process was calling fsleep. > > > Consuming like 16% of one of the 8 cores. ( amd ) > > > > There's not enough information to pinpoint anything. All I can say is that > > rust does build reliably in bulk builds on several architectures .. > > > > # uname -a > OpenBSD current.home 6.6 GENERIC#320 amd64 > > I will test the MP kernel > > PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND > 9521 root 100 231M 301M run fsleep1:01 35.16% rustc Don't build ports as root! It is not needed - an unnecessary big risk. > It takes ages to build ( AMD Athlon(tm) 5350 APU with Radeon(tm) R3, > 2046.39 MHz, 16-00-01 ) That particular process (35% cpu use, 1 minute cpu time) hasn't been running for long has it. If it was really stuck I'd expect a much higher TIME column. Rust is a massive resource drain, it takes me hours to build on a 3.8GHz xeon. I would strongly recommend using the packages unless you have a lot of patience.
Re: note to builder (rust)
On Mon, Oct 7, 2019 at 8:05 AM Stuart Henderson wrote: > > On 2019/10/07 07:46, sven falempin wrote: > > On Fri, Oct 4, 2019 at 6:30 PM Stuart Henderson > > wrote: > > > > > 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 > > > > > > > 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. > > > > > Hours, 16gb Ram, 64 bit multi core , process was calling fsleep. > > Consuming like 16% of one of the 8 cores. ( amd ) > > There's not enough information to pinpoint anything. All I can say is that > rust does build reliably in bulk builds on several architectures .. > # uname -a OpenBSD current.home 6.6 GENERIC#320 amd64 I will test the MP kernel PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND 9521 root 100 231M 301M run fsleep1:01 35.16% rustc It takes ages to build ( AMD Athlon(tm) 5350 APU with Radeon(tm) R3, 2046.39 MHz, 16-00-01 ) -- -- - Knowing is not enough; we must apply. Willing is not enough; we must do
Re: note to builder (rust)
On 2019/10/07 07:46, sven falempin wrote: > On Fri, Oct 4, 2019 at 6:30 PM Stuart Henderson wrote: > > > 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 > > > > > 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. > > > Hours, 16gb Ram, 64 bit multi core , process was calling fsleep. > Consuming like 16% of one of the 8 cores. ( amd ) There's not enough information to pinpoint anything. All I can say is that rust does build reliably in bulk builds on several architectures ..
Re: note to builder (rust)
On Fri, Oct 4, 2019 at 6:30 PM Stuart Henderson wrote: > 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 > > > 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. > > Hours, 16gb Ram, 64 bit multi core , process was calling fsleep. Consuming like 16% of one of the 8 cores. ( amd ) -- -- - Knowing is not enough; we must apply. Willing is not enough; we must do
Re: note to builder (rust)
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 > > 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.
note to builder (rust)
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 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
