-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Ensure SQL operations complete before reporting errors #16059
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
Conversation
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 137 Click here to see the affected service packages
Action takenFound 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
|
|
🔴 Tests failed during RECORDING mode: 🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR. |
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
Tests analyticsTotal tests: 137 Click here to see the affected service packages
🟢 All tests passed! View the build log |
SQL operations occasionally return transient internal errors while in the
RUNNINGstate (the backend automatically retries those errors internally). This PR ensures we don't error out prematurely when the operation is still in progress and likely to succeed.More context: b/457257721
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.