-
Notifications
You must be signed in to change notification settings - Fork 3.4k
test_binaryen fails on incoming branch + prebuilt SDK 1.37.21 #5634
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
Comments
The mode is added by recent pull request #5620 and the SDK just didn't support it yet. |
Does it work after updating the SDK? If not, maybe something went wrong in the update. |
No new SDK update after 1.37.21 yet, so no. |
Hmm, that's not good, maybe I don't understand how the emsdk pulls in binaryen updates. I tagged a 1.37.22 now. @juj, do binaryen updates need an emscripten version bump in order to take effect? It ignores the binaryen version in tools/ports/binaryen.py? |
PS: Incoming branch + binary SDK are not always guaranteed to work well together, this is why I closed this issue. The original post didn't explain the environment, sorry. |
This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 7 days. Feel free to re-open at any time if this issue is still relevant. |
sudo apt install python-pip && pip install --upgrade pip && pip install lit
unexpectedly causes test_binaryen fail:Any clue about why
--trap-mode
suddenly becomes unknown?The text was updated successfully, but these errors were encountered: