Closed smlambert closed 9 months ago
https://trss.adoptium.net/output/build?id=6572565e20748f006f878e53
Jenkins link: https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-mac-x64-temurin/430/console
Jenkins output size is larger than expected, so TRSS did not process it.
Ha, and I totally forgot that we had seen this same problem before: https://github.com/adoptium/temurin-build/issues/2835
This should be resolved once a fix for https://github.com/adoptium/temurin-build/issues/3562 is merged (see: https://github.com/adoptium/temurin-build/pull/3574).
Now resolved.
We now have test jobs running on dynamic Orka agents beginning for example in this pipeline https://trss.adoptium.net/resultSummary?parentId=657255cd20748f006f878e2b, and while test jobs are running and passing, they do not appear in the Grid view of trss.adoptium.net.
This happened before in https://github.com/adoptium/aqa-test-tools/issues/767 and was related to not having unique job numbers in Jenkins, have not checked if this is the case here, but noting it in this issue, in case we can spot the pattern of why it is happening (and in case this will not resolve itself).