-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Realtime compositions E2E tests flaky #5228
Comments
Bring in crossplane/crossplane-runtime#641 to see whether it helps with crossplane#5228. Signed-off-by: Nic Cope <nicc@rk0n.org>
FYI @sttts still seeing flakes after bumping runtime to include crossplane/crossplane-runtime#641. |
Per crossplane#5228 we know these tests fail most of the time. Running them on every CI job isn't helping catch anything we don't already know. It does make it harder to notice when other things fail, since we're becoming used to seeing the red x. I think we should disable these until they're less flaky. They're testing an alpha feature that is off by default. Signed-off-by: Nic Cope <nicc@rk0n.org>
Bring in crossplane/crossplane-runtime#641 to see whether it helps with crossplane#5228. Signed-off-by: Nic Cope <nicc@rk0n.org>
Per crossplane#5228 we know these tests fail most of the time. Running them on every CI job isn't helping catch anything we don't already know. It does make it harder to notice when other things fail, since we're becoming used to seeing the red x. I think we should disable these until they're less flaky. They're testing an alpha feature that is off by default. Signed-off-by: Nic Cope <nicc@rk0n.org>
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as |
/fresh |
#5651 might fix this - let's monitor for a while. |
What happened?
Anecdotally the realtime compositions E2E test seems to fail a lot more often than it passes. This means I'm becoming used to seeing the little ❌ next to every Crossplane PR (and on master). Ideally it would not be so flaky.
How can we reproduce it?
Run the E2E in GitHub Actions a few times.
What environment did it happen in?
Crossplane version:
The text was updated successfully, but these errors were encountered: