Refactor ARMv7 Scaleway host config #1204
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ie, stretch tests
rvagg
force-pushed
the
rvagg/armv7-scaleway
branch
from
06137ef to
d40fe97
Compare
|
I've disabled debian9 for now, getting random gcc-6 segfaults (seems to be mainly on crypto-related files), no idea what that's about or what it's related to (gcc, docker container base, armv7, our code, something else?). Easier to disable for now to get to green for folks and we'll try and figure it out later. We still have Wheezy for <10 and Jessie for >=10. |
|
You forgot the libuv job who got starved for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
the armv7-wheezy hosts were never in the ansible/ config but now they are. I've refactored the big Raspberry Pi changes from #1199 so that I could reuse the docker config. Now we have 3 new Scaleway ARMv7 machines running Ubuntu 16.04 with Docker on them and containers for Debian Wheezy, Jessie and Stretch (using Ubuntu for the host because I couldn't get around a strange Docker problem on Stretch). They are in node-test-commit-arm under the labels
debian7-docker-armv7,debian8-docker-armv7anddebian9-docker-armv7. I'm trying out the node-version-jenkins-plugin for this one which uses VersionSelectorScript.groovy as ci-release does to select which builders to use. For Node <10 it'll run tests on debian7 (Wheezy) and debian8 (Jessie) and for Node >=10 it'll run debian8 and debian9 (Stretch) (could run all 3 for <10 but they're not fast so two is more than enough).As I mentioned in #829, we're still locked in to a Raspbian gcc 4.8 on Wheezy and that's reflected in this PR as well, but thankfully we get a 4.9 in Jessie and a gcc 6 in Stretch so for Node 10 we're now only testing armv7 on gcc 4.9.2 minimum.