e2e tests are being observed to run for multiple hours in some failure cases where lots of output is presented. A specific instance for reference can be found here.
The core problem is error handling in the acvm.js component, but this is a problem in general if we print continuous output.
Key Points:
- The e2e container doesn't seem to exit upon encountering an error in the test. The error seen might be getting swallowed instead of being propagated
- The continuous noise from Anvil in the output prevents the 10-minute kill switch from terminating the test.
Actions to do or break-out into new issues:
- Ensure proper error propagation, especially concerning the wasm simulator error. Can change line 710 of acvm_js.js to throw an error and observe the behavior above, potentially running with --detectOpenHandles.
Done
e2e tests are being observed to run for multiple hours in some failure cases where lots of output is presented. A specific instance for reference can be found here.
The core problem is error handling in the acvm.js component, but this is a problem in general if we print continuous output.
Key Points:
Actions to do or break-out into new issues:
Done