What are you trying to do? Look ath the top level pipelinesRun a top level pipeline that kicks off the platform-specific subjobs and see the status reflected in the blocks in the pipeline overview
Expected behaviour: If the smoke test failes causing an overall fail status in the pipeline, then the corresponding square in the pipeline should show failed status
Observed behaviour:
This screenshot is from openjdk21-pipeline. The latest job (322) had the following which is what caused the overall red status of the job, but these are not reflected in the status blocks:
Note from @adamfarley: These failures were mostly caused by a git server outage failing multiple test subjobs. Full details here. This shouldn't affect status reporting, as git server outages are a common issue, and should be handled correctly. I'm providing this information to rule out "unusual scenario" as a potential cause for the reporting failure.
What are you trying to do? Look ath the top level pipelinesRun a top level pipeline that kicks off the platform-specific subjobs and see the status reflected in the blocks in the pipeline overview
Expected behaviour: If the smoke test failes causing an overall fail status in the pipeline, then the corresponding square in the pipeline should show failed status
Observed behaviour:
This screenshot is from openjdk21-pipeline. The latest job (322) had the following which is what caused the overall red status of the job, but these are not reflected in the status blocks:
Note from @adamfarley: These failures were mostly caused by a git server outage failing multiple test subjobs. Full details here. This shouldn't affect status reporting, as git server outages are a common issue, and should be handled correctly. I'm providing this information to rule out "unusual scenario" as a potential cause for the reporting failure.
Any other comments:
This seems like similar symptoms to https://github.com/adoptium/ci-jenkins-pipelines/issues/1068 which was resolved in https://github.com/adoptium/ci-jenkins-pipelines/pull/1071. Also related: Handling of the status of
ABORTEDjobs: https://github.com/adoptium/ci-jenkins-pipelines/issues/1097