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

request for post-mortem: dropping of centos5 in CI #1580

Closed
MylesBorins opened this issue Nov 20, 2018 · 4 comments
Closed

request for post-mortem: dropping of centos5 in CI #1580

MylesBorins opened this issue Nov 20, 2018 · 4 comments

Comments

@MylesBorins
Copy link
Contributor

Hey All,

We just finished promoting the release of 8.13.0 and were quickly notified that we were missing linux 32 binary tarballs.

Historically these have been built by centos 5. A bug in the matrix configuration stopped centos5 86 from building / testing in public CI and in turn building in our release CI.

After patching this bug we are finding that there is a bug in the libuv upgrade stopping things from building altogether.

The result of this is that we now have a pretty nasty firedrill where we need to figure out if we can even get 8.13.0 building on centos 5... if we can't we are going to need to do a quick 8.13.1 and figure out which version of libuv to revert. This could arguably be considered semver-minor though... so we may need to release an 8.14.0... pretty bad for LTS.

How did this get dropped across all the configs? This kind of silent failure is really bad.

@refack
Copy link
Contributor

refack commented Nov 20, 2018

References:
The groovy filter has been filtering out centos5 for >=8 form day 1

// Linux
if (builderLabel.indexOf('centos5') == 0 && nodeMajorVersion >= 8)
return false
if (builderLabel.indexOf('centos6') == 0 && nodeMajorVersion < 8)
return false

As described in #1153
following: #898

There's seems to be a disconnect about how we build node8...

tl;dr
Since we don't test, we didn't catch the libuv incompatibility introduced in:
libuv/libuv#1940 (comment)

Reevaluate PR:
#1579

@refack
Copy link
Contributor

refack commented Nov 20, 2018

New insights:
https://ci-release.nodejs.org/computer/release-digitalocean-centos6-x86-1/ machine was down so it did not build and silently failed.
We assumed it should build on centos5 but that's not supported anymore.

@MylesBorins can we close.

@MylesBorins
Copy link
Contributor Author

Yup

@rvagg
Copy link
Member

rvagg commented Nov 21, 2018

To clarify for anyone landing here via search or some other means: Node 8 was our cut-over version for CentOS 6, it's been building on 6 since 8.0.0 (see nodejs/node#12220 (comment)). We use GCC 4.8 and switched to CentOS 6 with GCC 6 (devtoolset-6) as of Node 10. CentOS 5 will be retired with Node 6 (afaik) in April.
This ticket is just a result of a misinterpretation of a failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants