test: check the clusterpedia apiserver before test cases #705
Conversation
This file contains 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
|
Hi @Iceber, DetailsInstructions for interacting with me using comments are available here. |
Signed-off-by: Iceber Gu <[email protected]>
Iceber
force-pushed
the
test_add_apiserver_check
branch
from
ba079cf to
34e9afc
Compare
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.
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
Both apiserver and clustersynchro manager trigger attempts to create database tables when they are started at the same time, and we have found from #702 that there are concurrency issues due to gorm design issues.
https://github.com/clusterpedia-io/clusterpedia/actions/runs/11732967909/job/33175301980?pr=702#step:4:818
go-gorm/gorm#6618
In production, it will automatically retry, but in testing, you need to add a check to avoid subsequent test failures.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: