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
A run of the nightly e2e tests failed overnight. Re-running it passed so the test appears to be possibly flaky. This test is still using gomega so it has this giant messy stack trace, but it looks like not all instances of the redis task got registered with Consul before the timeout.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
A run of the nightly e2e tests failed overnight. Re-running it passed so the test appears to be possibly flaky. This test is still using gomega so it has this giant messy stack trace, but it looks like not all instances of the redis task got registered with Consul before the timeout.
The text was updated successfully, but these errors were encountered: