-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
include wasm-test.sh in test-ci-all (almost) #4474
Conversation
69ab8ce
to
9f36a10
Compare
Any idea why this test might be failing now? It seems like it hangs and timeout kills it. The same thing happens locally on my machine, so I doubt it's running out of resources.
uses the same method and works perfectly. Seems like two rust tests in that hanged wasm-test are actualy passing so everything looks like it's working. |
very weird I have no idea why it would hang |
9f36a10
to
65c72c2
Compare
65c72c2
to
d70a081
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The last commit undoes a lot of the second to last one. I think you can squash them to just keep the changes that actually worked.
Yeah, I want these two separately because I want to be able to revert it when time comes to try again. It's a workaround for a blocker, ideally it would not be there at all. :( |
d70a081
to
ca9bf08
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK, issue created for TODO in test-ci-all
This required:
Unfortunately after tackling all the scripts & Nix issues, it turned out that wasm-tests (headless firefox?) just doesn't work when being run in GNU
parallel
orxargs -P
, and debugging it seems like lots of work.So we'll still run wasm-test separately, but at least it will now re-use build artifacts with the main build, so it should still be faster. And in the future we can try again.