-
Notifications
You must be signed in to change notification settings - Fork 71
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
Review state of canary in CI #244
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
@miladfarca informed me just yesterday about https://chromium-review.googlesource.com/c/v8/v8/+/4181030 requiring Python 3.8, which is the issue for the ImportErrors on ppc64le and s390x:
|
Compiler error on x86 Windows:
Edit: According to release CI, this appeared with V8 11.1.180. Previous successful build was done with V8 11.1.155. Failing asserts: In
In
|
I don't know what can explain the apparition of this error but I'll try to revert v8/v8@92a7385 as it's touching the memory chunk layout and is specific to 32bit msvc. |
Trying targos/node@6740c1c https://ci.nodejs.org/job/node-test-commit-windows-fanned/52766/ Edit: Looks like a red herring. It failed with the same error. |
/cc @nodejs/platform-windows |
I bisected V8 versions using CI. Down to this diff: v8/v8@11.1.176...11.1.177
|
If my analysis is right, there's only one change between 11.1.176 and 11.1.177: https://chromium-review.googlesource.com/c/v8/v8/+/4138254 |
@richardlau Is it going to be difficult to update? |
I don't think so, I just haven't had time to look at it yet. RHEL 8 does have packages for newer versions of Python although we may need other Ansible tweaks to make sure the builds use the newer Python as the system Python 3 will be 3.6. |
We did indeed need additional Ansible tweaks (use of |
Recent upstream V8 changes now require at least Python 3.8 to run the V8 test runner. Refs: nodejs/node-v8#244 (comment) Refs: https://chromium-review.googlesource.com/c/v8/v8/+/4181030
Windows arm64 build is broken:
It's due to this change: v8/v8@a696609 @nodejs/platform-windows-arm |
Previous thread: #234
The text was updated successfully, but these errors were encountered: