-
Notifications
You must be signed in to change notification settings - Fork 1k
Description
Our E2E tests have been failing randomly lately. These flaky failures make it difficult to determine if a genuine issue was introduced or if it’s just a test problem.
This issue is to collect and track intermittent E2E failures in one place. If you see a test fail and it passes on retry, please add a comment with:
- The test name
- A short error snippet or symptom
- Link to the CI run
Identified E2E test failures:
-
metrics presence testing
failure e2e link: https://github.com/karmada-io/karmada/actions/runs/18395251404/job/52413766044?pr=4574#step:6:742 -
Application failover testing with purgeMode gracefully
failure e2e link: https://github.com/karmada-io/karmada/actions/runs/18553955121/job/52887389171#step:6:444 -
Karmada Operator E2E test: PriorityClass configuration testing
-
Deploy workloads should be rejected in case of no enough quota left
-
Multi-Components: FederatedResourceQuota enforcement testing