Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Failed tests aren't showing in MacOS Sonoma #421

Open
bokobza opened this issue Dec 8, 2023 · 9 comments
Open

Failed tests aren't showing in MacOS Sonoma #421

bokobza opened this issue Dec 8, 2023 · 9 comments

Comments

@bokobza
Copy link

bokobza commented Dec 8, 2023

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.

@1997roylee
Copy link

same

@dimitrovmaksim
Copy link
Contributor

dimitrovmaksim commented Dec 18, 2023

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 graphprotocol/graph-tooling#1549, but it will probably take some time until everything is set.

@boyuanx
Copy link

boyuanx commented Jan 4, 2024

Running into the same issue here

@0xJem
Copy link

0xJem commented Jan 25, 2024

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.

@dimitrovmaksim
Copy link
Contributor

You can try the docker solution as a workaround https://thegraph.com/docs/en/developing/unit-testing-framework/#docker

@0xJem
Copy link

0xJem commented Jan 25, 2024

You can try the docker solution as a workaround https://thegraph.com/docs/en/developing/unit-testing-framework/#docker

Thank you!

@manumonti
Copy link

Same error here.

@clauBv23
Copy link

clauBv23 commented Feb 26, 2024

same here :(
docker helped

@bobo-k2
Copy link

bobo-k2 commented Mar 11, 2024

Same, same. Running test in Docker helped.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants