Repository navigation
Conversation
gcp: TestAccept/bundle/resources/postgres_endpoints/update_autoscaling aws: TestAccept/bundle/resources/postgres_endpoints/update_autoscaling Co-authored-by: Isaac <no-reply@databricks.com>
Contributor
|
Commit: Regression test reportSelected 1 changed tests (limit=20, 0 not selected) 2 tests: regression=0 unreleased=0 coverage=2 failing=0
|
Collaborator
✅ Integration test reportCommit: 1724e8b
Top 3 slowest tests (at least 2 minutes):
|
denik
marked this pull request as ready for review
November 15, 2026 04:10
denik
enabled auto-merge
November 15, 2026 04:37
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Record postgres requests with
print_requests.py --uniqueinbundle/resources/postgres_endpoints/update_autoscaling, so a retried request (an identical consecutive request) is recorded once.Why
On GCP the backend returned a transient 500 for
GET .../branches/mainduring the no-change deploy. The CLI retried the read on purpose (libs/retry,IsTransientReadinbundle/direct), and the retry showed up as an extra request inout.requests.no_change.json. The retry is correct behavior, so the recording should tolerate it. Same approach as #7511 and #7547 for apps.Not a regression from #7557 (that change retries create-operation polling) or from #7596 (testserver spec echo). The failing request is a plain remote-state read that has been retried for a while.
The current goldens have no consecutive duplicate requests, so
--uniquechanges only the traced command line in output.txt.Dashboard
Tests
Passed locally and on AWS (both DMS variants). The last commit asks CI to run the test on GCP and AWS.
This pull request and its description were written by Isaac.