Fix case failure caused by unstable results.#1071
Merged
my-ship-it merged 2 commits intoapache:mainfrom Apr 29, 2025
Merged
Conversation
songdongxiaoa2
force-pushed
the
main
branch
2 times, most recently
from
5c0c486 to
056aa31
Compare
added 2 commits
April 27, 2025 23:24
Error message: pg.InternalError: connection to server on socket "/tmp/.s.PGSQL.7001" failed: FATAL: the database system is not accepting connections DETAIL: Hot standby mode is disabled. FAILED: [Errno 104] Connection reset by peer Signed-off-by: Dongxiao Song <songdongxiao@hashdata.cn>
Signed-off-by: Dongxiao Song <songdongxiao@hashdata.cn>
my-ship-it
approved these changes
Apr 28, 2025
Member
|
please squash into one commit. |
yjhjstz
approved these changes
Apr 29, 2025
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
3 participants
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.
Fixes #ISSUE_Number
What does this PR do?
This pull request fixed two randomly occurring test failures:
1.GPORCA may or may not complain about falling back. Other cases ignored the notice, windows should ignore this too.
2.For debug build, promotion may not finish on time, which will cause subsequent sql failure.
Type of Change
Test Plan
No need to test, test case fix.
Impact
No, test case fix.
Performance:
No, test case fix.
User-facing changes:
No
Dependencies:
No