pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-single-node-upgrade (all) - 10 runs, 100% failed, 70% of failures match = 70% impact | |||
#1789909117956001792 | junit | 7 days 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: | |||
#1790748242175070208 | junit | 4 days 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: | |||
#1788643558408851456 | junit | 10 days 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: | |||
#1788902615812149248 | junit | 9 days 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: | |||
#1788631033952866304 | junit | 10 days 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: | |||
#1788526829372444672 | junit | 10 days 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: | |||
#1788216689674948608 | junit | 11 days 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: |
Found in 70.00% of runs (70.00% of failures) across 10 total runs and 1 jobs (100.00% failed) in 236ms - clear search | chart view - source code located on github