Wasmtime GitHub notifications bot (Apr 17 2020 at 12:48): Wasmtime GitHub notifications bot (Apr 17 2020 at 12:48):github-actions[bot] commented on Issue #1529:
Subscribe to Label Action
cc @bnjbvr
<details>
This issue or pull request has been labeled: "cranelift", "cranelift:module", "cranelift:wasm"Thus the following users have been cc'd because of the following labels:
- bnjbvr: cranelift
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
Wasmtime GitHub notifications bot (Apr 17 2020 at 15:21):rylev commented on Issue #1529:
@sunfishcode no it doesn't seem like there's good docs on when to use which log. From what I've seen out there
infois high-level logs that you'd want to show on every normal run of the programwarnis something went wrong but it's not fatal and should just be checked out when you have a chance
erroran error occured. It's not enough to crash the program but it's something that should be looked into ASAP
*debugany info that would be relevant to see the flow of the executing program
tracevery verbose logs. Generally not helpful for program wide debugging but useful when inspecting a small segment of the program.
Wasmtime GitHub notifications bot (Apr 17 2020 at 18:51):bjorn3 commented on Issue #1529:
It looks like CI failed to build because ld couldn't link, but it gave no discernible diagnostic message, just returned an exit code of 1. Hopefully just a transient failure.
That always happens for me when the disk is full.
Wasmtime GitHub notifications bot (Apr 17 2020 at 19:52):peterhuene commented on Issue #1529:
The failure is that CI is running out of disk space and we have some PRs up that will hopefully help mitigate the problem shortly.
Wasmtime GitHub notifications bot (May 06 2020 at 09:15):rylev commented on Issue #1529:
@peterhuene This should be good to go now. Sorry for the delay!
Last updated: Dec 13 2025 at 19:03 UTC