You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently observed some flakiness with e2e tests, resulting in a false negative rate of 50%, and wanted to avoid that by bumping the relevant timeouts.
However, we believe it is worth further investigation, especially why we observe failures while waiting for claims to become available.
What happened?
We recently observed some flakiness with e2e tests, resulting in a false negative rate of 50%, and wanted to avoid that by bumping the relevant timeouts.
However, we believe it is worth further investigation, especially why we observe failures while waiting for claims to become available.
An example run: https://github.com/crossplane/crossplane/actions/runs/6084680018/job/16507125031
How can we reproduce it?
Unfortunately it is not easily reproducable and happens sporatically with GitHub actions.
What environment did it happen in?
On master with CI.
The text was updated successfully, but these errors were encountered: