[backport -> release/3.6.x] tests: fix flakiness #12581
Merged
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
team-gateway-bot
added
cherry-pick kong-ee
StarlightIbuki
approved these changes
Feb 19, 2024
ADD-SP
approved these changes
Feb 19, 2024
|
Cherry-pick failed for |
|
Cherry-pick failed for Please cherry-pick the changes locally. git remote add upstream https://github.com/kong/kong-ee
git fetch upstream release/3.6.x
git worktree add -d .worktree/cherry-pick-12581-to-release/3.6.x-to-upstream upstream/release/3.6.x
cd .worktree/cherry-pick-12581-to-release/3.6.x-to-upstream
git checkout -b cherry-pick-12581-to-release/3.6.x-to-upstream
ancref=$(git merge-base 510b137268703dece7d0f1a00a439375d2ff9311 0f23b74b8e04a656ab1bfa4bc90efc17f0579583)
git cherry-pick -x $ancref..0f23b74b8e04a656ab1bfa4bc90efc17f0579583 |
|
I don't feel it is correct to cherry-pick a backporting PR. Is this intended? |
ADD-SP
removed
the
cherry-pick kong-ee
I am not sure, but I will cherry-pick and then backport to EE |
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.
Automated backport to
release/3.6.x, triggered by a label in #12580.Original description
Please REBASE and MERGE
Summary
The dynamic test scheduler exposed some issues by disrupting the order of the tests, some of which did not initialize the database or wrote incompatible data to the database, causing the Gateway instance to fail to start and causing the following test to fail.
Starting a Gateway instance even if it's not needed
spec/03-plugins/39-ai-request-transformer/01-transformer_spec.luaspec/03-plugins/40-ai-response-transformer/01-transformer_spec.luaThese two test sets start a Gateway instance to launch a mocking server, which can be replaced by the
spec.helpers.http_mock.The database was not initialized before starting the Gateway instance
spec/02-integration/09-hybrid_mode/02-start_stop_spec.luaStarting a service using a fixed port instead of a random port
Since the test sequence is disrupted and the port release is not real-time, this may cause the port to be occupied to the point where the test fails.
Checklist
changelog/unreleased/kongorskip-changeloglabel added on PR if changelog is unnecessary. README.mdIssue reference
KAG-3746