You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In compute_systematic_failures_on_metric() we are counting ignoreFailed tests for the total runs, which makes it impossible to have systematic failures by_k8s / by_postgres / by_platform given that failures == runs is always going to be False.
Note: There's only one case in which we could trigger systematic failures by_k8s / by_postgres / by_platform at the moment, and that's in case the Ginkgo suite didn't run at all (for example because the Cluster creation or any step that precedes the start of the e2e failed). In that case you would have a single failed Open Ginkgo report artifact which would make systematic failures by_k8s / by_postgres / by_platform properly trigger.
To fix this we should avoid including ignoreFailed tests in the total runs when calculating systematic failures.
The text was updated successfully, but these errors were encountered:
In
compute_systematic_failures_on_metric()
we are countingignoreFailed
tests for thetotal runs
, which makes it impossible to have systematic failuresby_k8s / by_postgres / by_platform
given thatfailures == runs
is always going to be False.Note: There's only one case in which we could trigger systematic failures
by_k8s / by_postgres / by_platform
at the moment, and that's in case the Ginkgo suite didn't run at all (for example because the Cluster creation or any step that precedes the start of the e2e failed). In that case you would have a single failedOpen Ginkgo report
artifact which would make systematic failuresby_k8s / by_postgres / by_platform
properly trigger.To fix this we should avoid including
ignoreFailed
tests in thetotal runs
when calculating systematic failures.The text was updated successfully, but these errors were encountered: