Nodejs 16/18 binaries are empty in releases about pkg-binaries HOT 10 CLOSED

Now I fix the upload thing and try to run the nodejs 18 build, should take aproximately 4h

thanks bro , I appreciate it, will wait for the new build then.

from pkg-binaries.

@kennethpdev I tried different ways to build nodejs 16/18 on armv7 without success, build never ends, I need to try with an RPI or another armv7 custom runner

from pkg-binaries.

FYI: https://github.com/yao-pkg/pkg-binaries/actions/runs/4142112503/jobs/7162400708

from pkg-binaries.

@robertsLando thanks for that information, also saw the runner, I think the build was a success but it failed to upload?

from pkg-binaries.

I uploaded it manually, luckily the runner is a custom runner so I have been able to access those files

from pkg-binaries.

Now I fix the upload thing and try to run the nodejs 18 build, should take aproximately 4h

from pkg-binaries.

You welcome 😄

from pkg-binaries.

Had to re-trigger nodejs 18 build cause it stopped with no reason, retried

from pkg-binaries.

looks like there is a problem with node18 build?

Error! Error: ENOENT: no such file or directory, open '/tmp/pkg.3f16f24465298a81b7d02149/node/out/Release/node'
Error: Process completed with exit code 2.

maybe you can do node16 for now.

from pkg-binaries.

The 16 is already online in releases, I need to retry with 18 another time....

from pkg-binaries.