-
Notifications
You must be signed in to change notification settings - Fork 73
v8: update to v10.7.193.13. #310
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
Conversation
Signed-off-by: Dhi Aurrahman <[email protected]>
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.
Those changes look good, but could you take a look at those failing tests? Both are timeouts, but it's possible that those are real regressions, so it would be good to test locally and compare against the current version of V8. Thanks!
Signed-off-by: Dhi Aurrahman <[email protected]>
Will do. But seems like the test also failed on master (on my local) :(. I need to check again when the time permits. |
Signed-off-by: Dhi Aurrahman <[email protected]>
Interesting, it passed here: https://github.com/dio/proxy-wasm-cpp-host/actions/runs/3179609270/jobs/5182308733 (stripped out some jobs, only on v8, Linux, x86_64). Hopefully here it will be fine too 🙏🏽 |
Signed-off-by: Dhi Aurrahman <[email protected]>
Signed-off-by: Dhi Aurrahman <[email protected]>
|
It's not crashing, it errors out because |
Signed-off-by: Dhi Aurrahman <[email protected]>
Ah, sorry I didn't check that line has |
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.
Thanks!
31508ba
to
54d6f0d
Compare
@dio sorry, it looks that I've messed this up by using the "update" button to merge with I removed that merge commit, but could you merge with |
@PiotrSikora no worries. Done. (I failed to check this PR earlier). |
@PiotrSikora @mathetake, sorry, seems like Wasmtime on macOS is flaky (?). Should I investigate or we can retry? |
Bazel on macOS on GitHub Actions is somehow flaky, it's unrelated to Wasmtime, since it's the toolchain detection that fails. I'll re-kick that test once V8 on macOS tests finish, since you can only re-kick failed tests after all tests complete. |
There was an error in V8 on macOS tests:
I've re-kicked it to make sure it's not a flake, but it looks like a real issue... maybe |
@PiotrSikora, yup I saw that will check again locally. |
Signed-off-by: Dhi Aurrahman [email protected]