-
-
Notifications
You must be signed in to change notification settings - Fork 709
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
Intermittent build failure: [FAILED ] install: node-capnp/node-capnp.ekam-manifest #3663
Comments
Interesting. Our CI does successfully build and run tests on Sandstorm, so I think all the dependencies should line up with: https://github.com/sandstorm-io/sandstorm/blob/master/.github/workflows/build.yml though the GitHub runners do preinstall a few things. I will see if I can get you an answer on this too, it's outside my personal expertise. |
Can you post the full build log? What happens if you run |
I have had the same problem on Ubuntu 20.04. If I run |
@tgupper, did you install meteor per https://docs.sandstorm.io/en/latest/install/#prerequisites ? |
Oh, it seems like I had not, sorry for that! I now executed all of the following, as described in the prerequisites:
The original problem still persists though:
|
@tgupper can you post the full build log? sometimes things further back in the log can provide some insight. |
Here you go. In addition to everything installed through the commands in the prerequisites, I now also installed glibc.
|
Drat, I don't see anything obvious. It should be pulling node.h out of the meteor dev bundle. What does |
When I execute
When I then execute
The file node.h exists in ./.meteor, but it doesn't seem like |
Have you tried running the build as a non-root user?
Quoting tgupper (2022-09-29 04:30:28)
… When I execute ./find-meteor-dev-bundle.sh, this is what I get:
user:~/sandstorm# ./find-meteor-dev-bundle.sh
Finding meteor-tool installation (can take a few seconds)...
You are attempting to run Meteor as the 'root' superuser. If you are
developing, this is almost certainly *not* what you want to do and will likely
result in incorrect file permissions. However, if you are running this command
in a build process (CI, etc.), or you are absolutely sure you know what you are
doing, set the METEOR_ALLOW_SUPERUSER environment variable or pass
--allow-superuser to proceed.
When I then execute ./find-meteor-dev-bundle.sh --allow-superuser, I
get:
Finding meteor-tool installation (can take a few seconds)...Please specify a pac
kage or release name to show information about it.
The file node.h exists in ./.meteor, but it doesn't seem like
./find-meteor-dev-bundle.sh points to it.
--
Reply to this email directly, [1]view it on GitHub, or [2]unsubscribe.
You are receiving this because you commented. Message ID:
***@***.***>
Verweise
1. #3663 (comment)
2. https://github.com/notifications/unsubscribe-auth/AAGXYPVXXXVCZSHRWAMODOLWAVHSJANCNFSM6AAAAAAQLJFDGQ
|
So I am seeing this issue, but it's intermittent. I did a test where the CI failed here, and then I re-ran CI and it succeeded. |
Here's an example of it failing in CI: https://github.com/sandstorm-io/sandstorm/actions/runs/3034304360/jobs/4883247374 |
I have tried the build instructions on Ubuntu 18, 20, 22, Debian latest, and Fedora 34 and latest. On Fedora the meteor install fails. On all the others, a variant of this error pops up:
Which dependency is missing? I have tried a few, but couldn't find the right one.
The easiest way to get more people to help out is to at least make sure that the project can easily be built.
The text was updated successfully, but these errors were encountered: