Support retry of flaky test: TestFullSyncExecution
MR: !1218 (merged)
Description
The following test under remote development is flaky and this must be resolved
https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/jobs/5741302622#L1601:
=== RUN TestFullSyncExecution
logger.go:130: 2023-12-13T09:53:08.007Z INFO starting full sync
logger.go:130: 2023-12-13T09:53:08.037Z INFO starting partial update
logger.go:130: 2023-12-13T09:53:08.068Z INFO starting partial update
logger.go:130: 2023-12-13T09:53:08.088Z INFO starting full sync
logger.go:130: 2023-12-13T09:53:08.099Z INFO starting partial update
logger.go:130: 2023-12-13T09:53:08.129Z INFO starting partial update
logger.go:130: 2023-12-13T09:53:08.164Z INFO starting full sync
logger.go:130: 2023-12-13T09:53:08.164Z INFO starting partial update
worker_test.go:52:
Error Trace: /src/internal/module/remote_development/agent/worker_test.go:52
Error: Not equal:
expected: 0x4
actual : 0x5
Test: TestFullSyncExecution
Messages: partial sync call count: 5
--- FAIL: TestFullSyncExecution (0.16s)
Technical Requirements
-
As there is no easy way to fix the flakiness of this test, retry the flaky test a fixed number of times until it succeeds. The retry logic should fail if none of the attempts result in a success
Edited by Hunar Khanna