Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Colour of platform-specific blocks in top level pipelines do not reflect failed status correctly #1098

Open
sxa opened this issue Aug 16, 2024 · 0 comments
Labels

Comments

@sxa
Copy link
Member

sxa commented Aug 16, 2024

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:
image

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 #1068 which was resolved in #1071.
Also related: Handling of the status of ABORTED jobs: #1097

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Todo
Development

No branches or pull requests

1 participant