-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
test-torque.tq failing source tarball builds for v12.11.0 (V8 7.7) #29709
Comments
Possibly related: #25095 I think it's the tarball that's the problem |
Actually yeah, I removed x86 from the unofficial-builds pipeline and the musl build broke with the same error: https://unofficial-builds.nodejs.org/logs/201909260213-v12.11.0/musl.log So the title is wrong for this issue, it's not x86 specific. |
Can reproduce by unpacking tarball, running configure, and then make (on Debian and Alpine):
|
I can reproduce on a
Very simple build options to reproduce: ./configure \
--prefix=/usr
make |
Part of the V8 7.7 update (#28918) added this: Line 85 in 4d2856e
Our source tarballs currently exclude everything in Line 1040 in d36b6f8
#29712 includes |
The V8 7.7 update didn't really add that line. It just made it explicit (the list was generated by a script before). |
For those wanting a quick fix for the current tarball:
~~While my build hasn't yet completed, it has been running for 20~ minutes now. It'd be great to know if more is needed to fix this present issue.~~ Build succeeded with above workaround. |
I suggest we fix that issue soon and release a patch release right after. |
Out of necessity (nodejs/node#29709), just in case tarball is broken again in the future.
Confirmed that @dylanaraps' method of including
I used it successfully to build on Alpine: https://github.com/mhart/alpine-node/blob/12.11.0/Dockerfile#L35 |
Builds from the source tarball were broken by the recent V8 upate to 7.7 as a file needed to build torque wasn't included in the source tarball as it resides in deps/v8/test. PR-URL: #29712 Fixes: #29709 Refs: #28918 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
EDIT: this is not x86 specific, see further comments below.
Holding up the unofficial-builds of v12.11.0 (we don't handle failures yet, so they're all blocked for now). Here's the failing build log for x86: https://unofficial-builds.nodejs.org/logs/201909252318-v12.11.0/x86.log
Key part:
We don't officially support them but have plenty of users, so if we can address this it would be really great. It's V8-related and I don't know how to go about assessing whether this is easy to address.
@nodejs/v8 any help getting this addressed on master would be greatly appreciated.
The text was updated successfully, but these errors were encountered: