Hi, On Thu, Feb 17, 2022 at 10:05:29PM +0100, Mark Wielaard wrote: > On Thu, Feb 17, 2022 at 08:46:01PM +0100, Marc via Gcc-rust wrote: > > ../gccrs/gcc/rust/hir -I ../../gccrs/gcc/rust/resolve -I > > ../../gccrs/gcc/rust/util -I ../../gccrs/gcc/rust/typecheck -I > > ../../gccrs/gcc/rust/lint > > ../../gccrs/gcc/rust/hir/tree/rust-hir-full-test.cc > > command timed out: 1200 seconds without output running [b'make', b'-j4'], > > attempting to kill > > process killed by signal 9 > > program finished with exit code -1 > > elapsedTime=1425.203557 > > > > Looks suspicious. Is it possible that the VM got stuck ? > > It did indeed. The machine only has 4GB of memory and 2GB swap. With > make -j4 there are 4 processes each taking ~1GB and it is just > swapping: > > 926 root 20 0 0 0 0 R 97.6 0.0 135:41.18 kswapd0 > 15794 buildbot 20 0 1539436 928056 0 D 2.4 24.5 1:41.92 cc1plus > 15817 buildbot 20 0 781108 674280 328 D 2.4 17.8 1:08.31 cc1plus > 15792 buildbot 20 0 1250264 763912 384 D 2.1 20.2 1:40.62 cc1plus > 15800 buildbot 20 0 1427104 784820 132 D 2.1 20.7 1:41.67 cc1plus > > I'll reconfigure with make -j3 to see if that helps.
It didn't. With -j3 the oom-killer kicks in (dunno why not with -j4): [1643873.684998] Out of memory: Killed process 16625 (cc1plus) total-vm:1764740kB, anon-rss:1040744kB, file-rss:0kB, shmem-rss:0kB, UID:998 pgtables:3464kB oom_score_adj:0 [1643873.992761] oom_reaper: reaped process 16625 (cc1plus), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB So now using make -j2 which does succeed. https://builder.wildebeest.org/buildbot/#/builders/58/builds/1655 Very odd. But apparently for some reason 4GB isn't enough anymore to use -j3 or -j4. Which is unfortunate because this board doesn't take more than 4GB memory. Cheers, Mark -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
