Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
If an E2E test fails, we will dump the cluster status through the following functions:
However, these log functions contain several assertions, and a failed assertion will block other cleanup steps in AfterEach. Incomplete cleanup can cause other E2E tests to fail.
For example, E2E test (#967) failed due to a flaky assert in gang scheduling. The afterEach status have no application in queue, which caused an assert function failed. Furthermore, the incompleted resources cleanup caused the following E2E tests to fail as well:
- simple_preemptor
- state_aware_app_scheduling
- user_group_limit
We should remove the assertions in those dump functions and just purely log the error messages.
Attachments
Issue Links
- Blocked
-
YUNIKORN-2291 Flaky e2e test
- Closed
- links to