-
Notifications
You must be signed in to change notification settings - Fork 2k
fix simultaneously creating a snapshot and updating the repository can potentially trigger an infinite loop #17532
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
fix simultaneously creating a snapshot and updating the repository can potentially trigger an infinite loop #17532
Conversation
3185a72
to
2a17f65
Compare
❌ Gradle check result for 2a17f65: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
2a17f65
to
0a9da2d
Compare
❌ Gradle check result for 6ebee6d: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
MinimumClusterManagerNodesIT.testThreeNodesNoClusterManagerBlock #14289 |
@andrross @ashking94 I'm very sorry to mention you again. Could someone help continue to review or merge the PR? There are too many flaky tests and Gradle check always fails. Your help is greatly appreciated. I want to continue #17488, but was blocked by this PR. |
Thanks for sticking with this @kkewwei. A lot of us are busy with the 3.0 release and as you've noted flaky tests are a major problem at the moment. |
❌ Gradle check result for 6ebee6d: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 6ebee6d: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
❌ Gradle check result for 6ebee6d: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: kkewwei <[email protected]> Signed-off-by: kkewwei <[email protected]>
6ebee6d
to
7415b92
Compare
…ject#17532) Signed-off-by: kkewwei <[email protected]> Signed-off-by: kkewwei <[email protected]> Signed-off-by: Tanishq Ranjan <[email protected]>
…ject#17532) Signed-off-by: kkewwei <[email protected]> Signed-off-by: kkewwei <[email protected]> Signed-off-by: Harsh Kothari <[email protected]>
…ject#17532) Signed-off-by: kkewwei <[email protected]> Signed-off-by: kkewwei <[email protected]> Signed-off-by: Harsh Kothari <[email protected]>
Description
Related Issues
Resolves #17531
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.