-
Notifications
You must be signed in to change notification settings - Fork 167
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
PPC: test-osuosl-ubuntu1404-ppc64_le-2 has strange linker issues #1815
Comments
/CC @mhdawson @sam-github |
I've pinged @sam-github to make sure this is on his radar. We were both out last week at the Collab summit. |
@miladfarca, you looked at this a bit? Did you have any ideas, or even manage to reproduce this? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@sam-github this is a separate issue I assume, the one I was looking at was related to the |
This comment has been minimized.
This comment has been minimized.
The history here is a bit confusing, because multiple issues are discussed. I hid @refack and @richardlau comments above that are related to #1820, just to make this easier to read. @miladfarca, we have discussed this linker error before, in slack:
Luckily (?) the linker problems stopped over the weekend, and my build passed and was merged (by someone else): nodejs/node#27834 But, there seems to be a real issue. Reviewing https://ci.nodejs.org/computer/test-osuosl-ubuntu1404-ppc64_le-2/builds, many failed with linker errors (though some with pty timeouts, as in #1820).
I'll go look at the .gyp file that Milad mentions in the workspace, and compare it to a clean build. Since the workers is offline, I should be able to redo the build in the workspace from ssh, and see if it fails to link for me, too. |
I copied the directory, re configured and compiled it from scratch and it worked fine. Seems like jenkins was interrupted mid compilation and the truncated Are we clearing cache/workspace properly before/after each build? |
Its possible the workspace isn't cleared, but its also possible that a bad build got ccached, which would cause the issue to come back over and over. I removed the .o file, cleared the ccache, and reenabled the machine.
EDIT: I'll leave this open until some builds pass on this machine. |
I just got a green build from the daily: https://ci.nodejs.org/computer/test-osuosl-ubuntu1404-ppc64_le-2/builds Perhaps this issue is resolved? |
https://ci.nodejs.org/computer/test-osuosl-ubuntu1404-ppc64_le-2/builds looks resolved, closing this. |
https://ci.nodejs.org/computer/test-osuosl-ubuntu1404-ppc64_le-2/ has been consistently failing with a linker error:
The text was updated successfully, but these errors were encountered: