containerd / runwasi

Facilitates running Wasm / WASI workloads managed by containerd
Apache License 2.0
1.01k stars 82 forks source link

Unable to compile shims #473

Closed SilenceShine closed 5 months ago

SilenceShine commented 5 months ago

b52dfda1e7a07c79c967f083363328a 1976ea4549e67c799c57911d6c55348

jprendes commented 5 months ago

The compilation process is being killed externally (ld terminated with signal 9 [Killed]). If you aren't killing it yourself, it could be that the machine is running out of memory. If running on the cloud, you could be hitting a timeout from your provider.

jprendes commented 5 months ago

Closing the issue as it's not a problem with the runwasi codebase. Feel free to reopen it if you have any follow up concerns.

Mossaka commented 5 months ago

the machine is running out of memory

I am curious to find out how much memory is required to compile runwasi

Mossaka commented 5 months ago

Output of /usr/bin/time -v cargo build --jobs 1

Command being timed: "cargo build --jobs 1"
    User time (seconds): 532.05
    System time (seconds): 57.50
    Percent of CPU this job got: 98%
    Elapsed (wall clock) time (h:mm:ss or m:ss): 9:55.95
    Average shared text size (kbytes): 0
    Average unshared data size (kbytes): 0
    Average stack size (kbytes): 0
    Average total size (kbytes): 0
    Maximum resident set size (kbytes): 1759328
    Average resident set size (kbytes): 0
    Major (requiring I/O) page faults: 598
    Minor (reclaiming a frame) page faults: 13547396
    Voluntary context switches: 46668
    Involuntary context switches: 5802
    Swaps: 0
    File system inputs: 46000
    File system outputs: 18733008
    Socket messages sent: 0
    Socket messages received: 0
    Signals delivered: 0
    Page size (bytes): 4096
    Exit status: 0