-
Notifications
You must be signed in to change notification settings - Fork 54
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
riscv64
build failed for v20.11.0
#106
Comments
This should be fixed now. From logs/202401101543-v20.11.0/build.log we can see we had some ECONNRESET errors trying to read from GitHub while running the indexer: + npx nodejs-dist-indexer --dist /home/nodejs/download/release --indexjson /home/nodejs/download/release/index.json --indextab /home/nodejs/download/release/index.tab
npx: installed 27 in 5.263s
Ignoring directory "v19.8.0" (can't decode dir contents)
Ignoring directory "lost+found" (can't decode ref)
{ Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
(ignoring error fetching V8 version for node/v20.11.0)
{ Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
(ignoring error fetching uv version for node/v20.11.0)
{ Error: Client network socket disconnected before secure TLS connection was established
at TLSSocket.onConnectEnd (_tls_wrap.js:1125:19)
at Object.onceWrapper (events.js:286:20)
at TLSSocket.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
code: 'ECONNRESET',
path: null,
host: 'raw.githubusercontent.com',
port: 443,
localAddress: undefined }
(ignoring error fetching OpenSSL version for node/v20.11.0)
{ Error: Client network socket disconnected before secure TLS connection was established
at TLSSocket.onConnectEnd (_tls_wrap.js:1125:19)
at Object.onceWrapper (events.js:286:20)
at TLSSocket.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
code: 'ECONNRESET',
path: null,
host: 'raw.githubusercontent.com',
port: 443,
localAddress: undefined }
(ignoring error fetching LTS version for node/v20.11.0)
{ Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
(ignoring error fetching modules version for node/v20.11.0)
{ Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
(ignoring error fetching npm version for node/v20.11.0)
++ date
+ echo 'Finished build @ Wed Jan 10 20:39:15 UTC 2024'
Finished build @ Wed Jan 10 20:39:15 UTC 2024 I've removed the v20.11.0 entries from npx nodejs-dist-indexer --dist /home/nodejs/download/release --indexjson /home/nodejs/download/release/index.json --indextab /home/nodejs/download/release/index.tab |
To clarify -- the missing "LTS" status has been fixed. The riscv build failure is unrelated. cc @nodejs/platform-riscv64 |
riscv64
build failed for v20.11.0
(preventing latest LTS from updating)riscv64
build failed for v20.11.0
Thanks! If I understand correctly, the build failure still needs a look, so I'll leave this open for now. |
Hmmm I wonder if something has happened between those two versions which means the version of the cross-compiler is no longer suitable for building. |
Noting that the master build of v22.0.0 builds ok with the latest (native) compiler on Ubuntu when I build on a real board which would certainly indicate that an older cross-compiler may be the cause of this. |
I think that's because nodejs/node#50552 was not identified as applying to v21 only. |
Yes, it shouldn't be applied to v20. |
This reverts commit bc2ebb9, which shouldn't be applied to v20.x. Fix nodejs/unofficial-builds#106
I opened a revert PR: nodejs/node#51495 |
This reverts commit bc2ebb9, which shouldn't be applied to v20.x. Fix nodejs/unofficial-builds#106 PR-URL: #51495 Fixes: nodejs/unofficial-builds#106 Reviewed-By: Franziska Hinkelmann <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Stewart X Addison <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
We have a fork that builds with Ubuntu 22.04 cross-compiler. We'd love to see this change upstream. |
The revert was included in Node.js 20.12.0. |
Build of v22.1.0 is still failing
Is this a problem with v8? ps: I'm trying to build with ubuntu 22.04 gcc-riscv64-linux-gnu. |
nodejs/node#52678 -- may be fixed by nodejs/node#52888. |
I noticed thatv20.11.0
isn't listed as an LTS build in index.json. That's probably because theriscv64
build failed, since it means not all platforms would be able to update. I don't use theriscv64
build myself, but our automation looks for the latest LTS and that means it's still stuck onv20.10.0
:)Build log: https://unofficial-builds.nodejs.org/logs/202401101543-v20.11.0/riscv64.log
The errors look like this:
There are some other errors, but I think they're all a consequence of the above.
Unfortunately I don't know where to go to fix it, where to go to submit a fix or how to test it even if I did, so I hope someone else can have a look!
The text was updated successfully, but these errors were encountered: