| pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.20-e2e-gcp-ovn-etcd-scaling (all) - 2 runs, 100% failed, 50% of failures match = 50% impact | |||
| #2094510630919737344 | junit | 48 minutes ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 2 unexpected clusteroperator state transitions during e2e test run. These did not match any known exceptions, so they cause this test-case to fail: | |||
| pull-ci-openshift-cluster-control-plane-machine-set-operator-release-4.20-e2e-vsphere-ovn-etcd-scaling (all) - 2 runs, 100% failed, 50% of failures match = 50% impact | |||
| #2094510630978457600 | junit | 3 hours ago | |
# [bz-Monitoring] clusteroperator/monitoring should not change condition/Available 2 unexpected clusteroperator state transitions during e2e test run. These did not match any known exceptions, so they cause this test-case to fail: | |||
| aggregator-periodic-ci-openshift-release-main-nightly-5.1-e2e-metal-ipi-ovn-ipv4 (all) - 2 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2094434998026244096 | junit | 6 hours ago | |
# openshift-tests.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should | |||
| #2094435006133833728 | junit | 6 hours ago | |
# openshift-tests.[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available name: '[Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should | |||
| periodic-ci-openshift-multiarch-main-nightly-4.23-ocp-e2e-ovn-powervc-multi-p-p (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #2094334679116156928 | junit | 15 hours ago | |
# [Monitor:legacy-cvo-invariants][bz-Monitoring] clusteroperator/monitoring should not change condition/Available 2 unexpected clusteroperator state transitions during (upgrade=false) e2e test run. These did not match any known exceptions, so they cause this test-case to fail: | |||
Found in 0.02% of runs (0.08% of failures) across 33316 total runs and 9408 jobs (19.60% failed) in 349ms - clear search | chart view - source code located on github