TRSS Shows "UNSTABLE" Instead of "FAILED" for Fully Failed Test Jobs

During the recent release testing, observed that some test jobs which fully failed were reported as UNSTABLE (yellow) in TRSS instead of FAILED (red). This could be a bit misleading, as it gives the impression that the job ran tests with tests that didnt pass, rather than failed job.

🔍 Affected Job:
[Test_openjdk11_j9_extended.functional_ppc64le_linux_fips140_3_openjceplusfips #41](https://hyc-runtimes-jenkins.swg-devops.com/job/Test_openjdk11_j9_extended.functional_ppc64le_linux_fips140_3_openjceplusfips/41/)
🔗 TRSS Result Summary:
https://trssrtp1.fyre.ibm.com/resultSummary?parentId=6855a584150950132c63aec4


🔍 Affected Job:
[Test_openjdk21_j9_extended.perf_ppc64le_linux #112](https://hyc-runtimes-jenkins.swg-devops.com/job/Test_openjdk21_j9_extended.perf_ppc64le_linux/112/consoleFull)

🔗 TRSS Result Summary:
https://trssrtp1.fyre.ibm.com/resultSummary?parentId=68619dd8376286111a6a8eaa


Start by reviewing the two linked Jenkins jobs and their TRSS result summaries to compare the reported job outcomes. Trace where fully failed jobs are classified as UNSTABLE rather than FAILED. Done means both reported examples, and equivalent fully failed jobs, are shown as FAILED.

Written by the indexing model from the issue text.