Open bokobza opened 8 months ago
same
So far it seems this issue is related to a dependency wasmtime
which is locked to version 0.27.0
by the graph-node dependency, and when a test fails, e.g the AssemblyScript code throws an error, it causes some kind of memory error. Unfortunately there's not much we can do, because this means graph-node has to be updated to newer versions of the crate, which includes multiple breaking changes. Also further support/development will be handled in the graph-tooling repo https://github.com/graphprotocol/graph-tooling/pull/1549, but it will probably take some time until everything is set.
Running into the same issue here
Was anyone able to find a workaround to this? It's hard to check whether there are regressions if we can't trust the tests to fail.
You can try the docker solution as a workaround https://thegraph.com/docs/en/developing/unit-testing-framework/#docker
You can try the docker solution as a workaround https://thegraph.com/docs/en/developing/unit-testing-framework/#docker
Thank you!
Same error here.
same here :( docker helped
Same, same. Running test in Docker helped.
For some strange reason, and only on MacOS Sonoma, when a test fails, it looks like the rest of the tests are aborted and no error is showing. For example in a series of 10 test, if there a failure in the 5th test, only 4 tests are showing as passed and there is no indication that there was a failure.
This is with Matchstick 0.6.0. Node 18 or 20 makes no difference.