Describe the bug
During the execution of make test locally or on CI runners, the instautoctrl e2e test suite (TestInstautoctrl) frequently fails due to timeouts when waiting for newly created resources.
This is the typical timeout error:
[FAILED] Timed out after 60.000s.
Expected
<bool>: false
to be true
In [It] at: /home/crownlabs/CrownLabs/operators/pkg/instautoctrl/test_e2e/instautoctrl_suite_test.go:146
The timeout happens in the doesEventuallyExists helper because the test client reads from a cache. On slower machines or CPU-throttled GitHub Actions runners, the informer cache takes longer than 60 seconds to sync the newly created resources, resulting in a random timeout failure.
Describe the bug
During the execution of make test locally or on CI runners, the instautoctrl e2e test suite (TestInstautoctrl) frequently fails due to timeouts when waiting for newly created resources.
This is the typical timeout error:
The timeout happens in the doesEventuallyExists helper because the test client reads from a cache. On slower machines or CPU-throttled GitHub Actions runners, the informer cache takes longer than 60 seconds to sync the newly created resources, resulting in a random timeout failure.