Solved cargo-c compile fails near the end with SIGKILL

ericx

ericx

devel/cargo-c (v. 0.9.28) compile has a "Building" progress bar and at 344/348 the process appears to have stopped because of a watchdog timer?

Initially the vast majority of cargo jobs complete in about a second. Several appear to take as much as 5. It does appear that as the last job in the progress bar approaches, they take longer. After 340, several run just under 30 seconds. 343 runs for just under 3 minutes; but #344 appears to receive a signal at what looks to be 30 seconds.

Code: 
warning: build failed, waiting for other jobs to finish...
error: could not compile `cargo-c` (bin "cargo-ctest")
                        
Caused by:
  process didn't exit successfully: `CARGO=/usr/local/bin/cargo CARGO_BIN_NAME=cargo-ctest ... -L native=/usr/local/lib` (signal: 9, SIGKILL: kill)

Is my system simply too slow?
Is there a timing knob I can push up?
 
I think you are correct:

Code: 
# dmesg
  ...
swap_pager: out of swap space
swp_pager_getswapspace(11): failed
pid 3749 (rustc), jid 0, uid 0, was killed: failed to reclaim memory
pid 3750 (rustc), jid 0, uid 0, was killed: failed to reclaim memory
pid 897 (smbd), jid 0, uid 0, was killed: failed to reclaim memory
swp_pager_getswapspace(3): failed
 
for the record: Cranked RAM on the FreeBSD VM up from 4 to 8 GB and compile finishes without error.
 
You must log in or register to reply here.
Back
Top