search

scylladb / argus

Apache License 2.0
4 stars 11 forks source link

On Releases dashboard Argus did not mark a rolling upgrade test run as failed when one of releases upgrade failed #488

Open dimakr opened 4 weeks ago

dimakr commented 4 weeks ago

Argus did not mark a rolling upgrade test run as failed on the Releases dashboard, even though one of the upgrade tasks failed (the rolling upgrade pipeline runs several upgrade tasks in parallel, for a set of base_versions, which all share the same run number in Argus). But when run itself is opened the failed the task is shown as failed as expected. However, when the test run itself is opened, the failed task is shown as failed as expected.

Example of a 'successful' run on the Releases dashboard: Image Which in fact has one failed task: Image

The issue could falsely indicate that there were no problems in the test run, when analyzing release candidate results in the Releases dashboard.

vponomaryov commented 4 weeks ago

@dimakr it must have been filed here: https://github.com/scylladb/argus/issues

dimakr commented 4 weeks ago

@dimakr it must have been filed here: https://github.com/scylladb/argus/issues

I see. @k0machi I don't have rights, but maybe you can transfer this issue to argus repo? (if not I'll re-create it)

k0machi commented 4 weeks ago

This could be a regression due to a recent stat rework, I will check.