Release report summary showing in-accurate report from previous run ?

[andrew-m-leonard]

Running a release report summary on http://20.90.182.165/releaseSummary?parentId=653a8b3a20748f006f9329f2&buildName=release-openjdk17-pipeline #46

Showed the following, however none of the sign_* and create_installer_windows had failed, they had failed in the previous run of this job, so it seems it's picking up the previous run or from some cache of the previous result? is this correct? :

Release Summary Report for release-openjdk17-pipeline

Report generated at: Fri, 27 Oct 2023 08:54:36 GMT

TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/release-openjdk17-pipeline/46/
Started by upstream project "build-scripts/utils/releaseTrigger_jdk17u" build number 3054 at 26/10/2023, 16:45:12

---

create_installer_windows ❌ undefined ❌

jdk17u-release-windows-x86-32-temurin ⚠️ UNSTABLE ⚠️

sign_build ❌ undefined ❌

sign_installer ❌ undefined ❌

sign_temurin_gpg ❌ undefined ❌

---

Test_openjdk17_hs_extended.openjdk_x86-32_windows ⚠️ UNSTABLE ⚠️

Test_openjdk17_hs_extended.openjdk_x86-32_windows_testList_0 ⚠️ UNSTABLE ⚠️
jdk_tools_2 => deep history 7/20 passed | possible issues
jvm_compiler_2 => deep history 0/25 passed | possible issues

[smlambert]

This is because the functional ID used to query Jenkins does not have access to those jobs. Please see adoptium/ci-jenkins-pipelines#236

I will close this issue as a dup of ci-jenkins-pipelines/issues/236