Skip to content
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

Release ARMv7 machines down #1946

Closed
BethGriggs opened this issue Oct 8, 2019 · 5 comments
Closed

Release ARMv7 machines down #1946

BethGriggs opened this issue Oct 8, 2019 · 5 comments

Comments

@BethGriggs
Copy link
Member

Noticed when building v8.16.2 release - https://ci-release.nodejs.org/label/debian7-docker-armv7/

Also, the pi-docker builds failed with a Git issue - https://ci-release.nodejs.org/job/iojs+release/nodes=pi1-docker/4739/console I've cleaned the workspace and will try and rebuild.

@mhdawson
Copy link
Member

mhdawson commented Oct 8, 2019

@BethGriggs I just restarted the agent on -1 and it seems to be back, will restart on -2 as well.

@mhdawson
Copy link
Member

mhdawson commented Oct 8, 2019

Both are back up now, closing. Please re-open if it's not resolved.

@BethGriggs
Copy link
Member Author

I'm still struggling to get a pi-docker Release build through (I think that job produces the armv6 builds) - https://ci-release.nodejs.org/job/iojs+release/4746/nodes=pi1-docker/

The job fails with a Git checkout error - but wiping the workspace has resulted in the Git stage timing out. Any suggestions, and/or could someone take a look at the machines that serve that job?

@BethGriggs BethGriggs reopened this Oct 9, 2019
@BethGriggs
Copy link
Member Author

The build is now past the Git checkout - but i'll leave this issue open until it completes

@rvagg
Copy link
Member

rvagg commented Oct 12, 2019

looks like it's all finished now - just be aware in future that repopulating a cleaned workspace on these machines is quite expensive so will extend your build time by quite a bit. Perhaps that was the best course in this case though.

With 8.x going away this problem should get resolved because we switched to cross compiling our release builds for 10+.

@rvagg rvagg closed this as completed Oct 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants