Jenkins linking to wrong child Job

[mmarchini]

For this run https://ci.nodejs.org/job/node-test-pull-request/29714/ I got a failure on parallel/test-tls-keylog-tlsv13 on ubuntu1804_sharedlibs_openssl110_x64. While investigating, I noticed that the failing ubuntu1804_sharedlibs_openssl110_x64 job linked on Jenkins is not the job I started:

(https://ci.nodejs.org/job/node-test-commit-linux-containered/18606/)

(https://ci.nodejs.org/job/node-test-commit-linux-containered/18606/)

Am I missing something? Should I ignore ubuntu1804_sharedlibs_openssl110_x64 because the icon is transparent (in which case we need update ncu-ci)?

[rvagg]

This is a Jenkins UI failure ... it's slightly transparent meaning it wasn't run on this job, https://github.com/nodejs/build/blob/master/jenkins/scripts/VersionSelectorScript.groovy excludes openssl110 for >= 12.

I know this is not ideal, but to be absolutely sure if you're confused at this in future, look at the build number, it should carry over to the direct child builds. So you're looking at node-test-commit-linux-containered 18606, but hover over the openssl110 job and you'll see it linking to 18601. If it's not 18606 then it's not relevant.

We do use a custom theme, from http://afonsof.com/jenkins-material-theme/, it's probably quite possible to tweak the CSS to make this better. We manually paste in CSS to our Jenkins instances from that theme generator so it's just as easy to edit the CSS.

[mmarchini]

Thanks. I'll see if we can improve this on ncu-ci as well.

[richardlau]

https://issues.jenkins-ci.org/browse/JENKINS-11373 (marked wontfix 😞 )

[mmarchini]

Edit: seems like it started my build now?

---

Ok, I understand the rationale here (and probably there's nothing we can do), but this makes no sense (build shows as still running, but subjob was not started by it):

[mmarchini]

probably not actionable