Open ailisp opened 3 years ago
@ailisp what is the status of this issue?
@bowenwang1996 still need it, don't have update recently
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
@matklad do we still need this?
Yes, I am not positive that we have all the tests we need here. I'll assign to @nagisa, as they have better understanding where the combined our+wasmer testing is enough.
I believe it to be genuinely needed still. The wasmer codebase doesn't seem to have any tests that would test precisely for at least some of the codes, even though they may be fairly straightforward to reproduce. Which also means that it likely doesn't have any tests for tricky corner cases for these codes either.
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
For wasmer 0.x runner, it's defined in near-vm-errors/src/lib.rs. For wasmer 1.x, it's defined in wasmer/lib/vm/src/trap/trapcode.rs. For both runner, the trap cases are not fully covered in our vm tests and should be.