Some test jobs not displaying in Grid & tree views

[smlambert]

As mentioned in this Slack thread, this Grid view does not display the AIX build/test jobs, nor does it display the smoke tests.

After that pipeline run, a later pipeline for JDK 8 was then run and no build/test jobs are displaying in it (see Grid view).

This thread in the infra channel indicates no problems with space:

root@trss:~# df -h | grep -v loop | grep -v tmpfs
Filesystem      Size  Used Avail Use% Mounted on
udev            7.6G  302M  7.3G   4% /dev
/dev/nvme1n1p1  7.7G  6.8G  931M  89% /
/dev/nvme0n1p2  167G   14G  145G   9% /data
root@trss:~# 

[llxia]

TRSS has jdk17u-release-aix-ppc64-temurin #1 in its database under the root build https://ci.adoptopenjdk.net/job/build-scripts/job/release-openjdk17-pipeline/10, not 17. (TRSS API link for jdk17u-release-aix-ppc64-temurin #1 data)

It looks like the same build with the same build number (jdk17u-release-aix-ppc64-temurin #1) was trigger twice.

• First time (Jan 12th):

The root build 10 https://ci.adoptopenjdk.net/job/build-scripts/job/release-openjdk17-pipeline/10/ triggered jdk17u-release-aix-ppc64-temurin build number 1

• Second time (Jan 15th):

Another root build 16 https://ci.adoptopenjdk.net/job/build-scripts/job/release-openjdk17-pipeline/16/ triggered the same jdk17u-release-aix-ppc64-temurin again with same build number 1.

At this point, the Jenkins links are broken as well. The root build 10 links to jdk17u-release-aix-ppc64-temurin/1/ which was the test build triggered from the root build 17.

TRSS assumes combination of build name and build number from same Jenkins is unquie. Instead of treating the second jdk17u-release-aix-ppc64-temurin #1 as a new build, it treated as an update to the child of first build - release-openjdk17-pipeline/10 . This is the reason why we do not see jdk17u-release-aix-ppc64-temurin/1/ under root build 17, but in root build 10.

[smlambert]

Thanks for the explanation @llxia - adding this issue to the general release retrospective.

[smlambert]

Closing this as there is not a change that would happen in this code base, but rather a process change to either not delete entire pipelines, or if we do, then delete the matching contents in the TRSS database.