fix(riscv64): switch to jammy and use node v24 with glibc 2.33 support

[kxxt]

Because v24 riscv64 binaries in node.js unofficial builds requires glibc 2.38, fix it by:

• Switch to ubuntu jammy and drop focal image.
  • The cross toolchain in jammy ships glibc 2.35 while the one in old focal ships glibc 2.31.
• Use my cross-compiled riscv64 node.js binaries that supports glibc 2.33.
  • If a new version is needed in the future, please request a new build by opening an issue in https://github.com/riscv-forks/node-riscv

Tested in https://github.com/kxxt/vscodium/actions/runs/29000195155/job/86060642656

[daiyam]

Can you move focal-devtoolset-riscv64 into archived?

From our previous conversion, is focal-ppc64le working correctly since it's also using nodesource?

[kxxt]

Can you move focal-devtoolset-riscv64 into archived?

Done.

From our previous conversion, is focal-ppc64le working correctly since it's also using nodesource?

I think it is working correctly since focal-riscv64 is used for the desktop application build, where the native node addons are not compiled against the node binary/headers. Thus it does not need to use a native riscv64 node binary running under QEMU emulation. Instead, in that case, the native node addons are compiled against the electron binary/headers.

[kxxt]

From our previous conversion, is focal-ppc64le working correctly since it's also using nodesource?

I think it is working correctly since focal-riscv64 is used for the desktop application build, where the native node addons are not compiled against the node binary/headers. Thus it does not need to use a native riscv64 node binary running under QEMU emulation. Instead, in that case, the native node addons are compiled against the electron binary/headers.

Just in case, I examined https://github.com/VSCodium/vscodium/releases/download/1.126.04524/VSCodium-linux-riscv64-1.126.04524.tar.gz to confirm it:

file windows.node
windows.node: ELF 64-bit LSB shared object, UCB RISC-V, RVC, double-float ABI, version 1 (SYSV), dynamically linked, BuildID[sha1]=cc4fa9d1f23f3cb789ce852eef6db33298c39293, not stripped

[kxxt]

It appears that the Publish Image workflow was cancelled: https://github.com/VSCodium/vscode-linux-build-agent/actions/runs/29020935233. I will wait until the new image is published before opening the next PR at VSCodium/vscodium main repo.

[daiyam]

The new image should be available (https://github.com/VSCodium/vscode-linux-build-agent/actions/runs/29021429468)

[daiyam]

I cancelled the workflow because the validation was acting weirdly. Some were validated some others weren't.

[kxxt]

I cancelled the workflow because the validation was acting weirdly. Some were validated some others weren't.

Thanks for the explanation! I have opened the next PR at VSCodium/vscodium#2921.