ADBDEV-4798: Fix gprecoverseg behave test#874
Merged
KnightMurloc merged 1 commit intoadb-7.1.0from Feb 28, 2024
Merged
Conversation
In the scenario "gprecoverseg should not give warning if pg_basebackup is running for the up segments", after stopping the primary segments, there is no waiting for switching to mirrors, and therefore the step "the user suspend the walsender on the primary on content 2" fails. This patch adds the "user can start transactions" step after stop primary segments to wait for switching to mirrors. As is done in other scenarios.
|
Failed job Resource group isolation tests 7: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1108199 |
Stolb27
approved these changes
Feb 28, 2024
KnightMurloc
added a commit
that referenced
this pull request
Jul 4, 2024
In the scenario "gprecoverseg should not give warning if pg_basebackup is running for the up segments", after stopping the primary segments, there is no waiting for switching to mirrors, and therefore the step "the user suspend the walsender on the primary on content 2" fails. This patch adds the "user can start transactions" step after stop primary segments to wait for switching to mirrors. As is done in other scenarios.
KnightMurloc
added a commit
that referenced
this pull request
Apr 21, 2025
In the scenario "gprecoverseg should not give warning if pg_basebackup is running for the up segments", after stopping the primary segments, there is no waiting for switching to mirrors, and therefore the step "the user suspend the walsender on the primary on content 2" fails. This patch adds the "user can start transactions" step after stop primary segments to wait for switching to mirrors. As is done in other scenarios.
KnightMurloc
added a commit
that referenced
this pull request
Apr 21, 2025
In the scenario "gprecoverseg should not give warning if pg_basebackup is running for the up segments", after stopping the primary segments, there is no waiting for switching to mirrors, and therefore the step "the user suspend the walsender on the primary on content 2" fails. This patch adds the "user can start transactions" step after stop primary segments to wait for switching to mirrors. As is done in other scenarios.
KnightMurloc
added a commit
that referenced
this pull request
Apr 21, 2025
In the scenario "gprecoverseg should not give warning if pg_basebackup is running for the up segments", after stopping the primary segments, there is no waiting for switching to mirrors, and therefore the step "the user suspend the walsender on the primary on content 2" fails. This patch adds the "user can start transactions" step after stop primary segments to wait for switching to mirrors. As is done in other scenarios.
KnightMurloc
added a commit
that referenced
this pull request
Apr 23, 2025
In the scenario "gprecoverseg should not give warning if pg_basebackup is running for the up segments", after stopping the primary segments, there is no waiting for switching to mirrors, and therefore the step "the user suspend the walsender on the primary on content 2" fails. This patch adds the "user can start transactions" step after stop primary segments to wait for switching to mirrors. As is done in other scenarios.
KnightMurloc
added a commit
that referenced
this pull request
Apr 25, 2025
In the scenario "gprecoverseg should not give warning if pg_basebackup is running for the up segments", after stopping the primary segments, there is no waiting for switching to mirrors, and therefore the step "the user suspend the walsender on the primary on content 2" fails. This patch adds the "user can start transactions" step after stop primary segments to wait for switching to mirrors. As is done in other scenarios. (cherry picked from commit e38f572)
KnightMurloc
added a commit
that referenced
this pull request
Apr 29, 2025
In the scenario "gprecoverseg should not give warning if pg_basebackup is running for the up segments", after stopping the primary segments, there is no waiting for switching to mirrors, and therefore the step "the user suspend the walsender on the primary on content 2" fails. This patch adds the "user can start transactions" step after stop primary segments to wait for switching to mirrors. As is done in other scenarios. (cherry picked from commit e38f572)
KnightMurloc
added a commit
that referenced
this pull request
May 5, 2025
In the scenario "gprecoverseg should not give warning if pg_basebackup is running for the up segments", after stopping the primary segments, there is no waiting for switching to mirrors, and therefore the step "the user suspend the walsender on the primary on content 2" fails. This patch adds the "user can start transactions" step after stop primary segments to wait for switching to mirrors. As is done in other scenarios. (cherry picked from commit e38f572)
KnightMurloc
added a commit
that referenced
this pull request
May 12, 2025
In the scenario "gprecoverseg should not give warning if pg_basebackup is running for the up segments", after stopping the primary segments, there is no waiting for switching to mirrors, and therefore the step "the user suspend the walsender on the primary on content 2" fails. This patch adds the "user can start transactions" step after stop primary segments to wait for switching to mirrors. As is done in other scenarios. (cherry picked from commit e38f572)
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.
Fix gprecoverseg behave test
In the scenario "gprecoverseg should not give warning if pg_basebackup is
running for the up segments", after stopping the primary segments, there is no
waiting for switching to mirrors, and therefore the step "the user suspend the
walsender on the primary on content 2" fails.
This patch adds the "user can start transactions" step after stop primary
segments to wait for switching to mirrors. As is done in other scenarios.