Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests(ai-plugins): fix flaky latency assertion #13558

Merged
merged 1 commit into from
Aug 22, 2024

Conversation

flrgh
Copy link
Contributor

@flrgh flrgh commented Aug 22, 2024

The way this latency is measured in the code is not granular enough to guarantee that it will always produce a non-zero result, so the assertion is changed from > to >=.

KAG-5251

The way this latency is measured in the code is not granular enough to
guarantee that it will always produce a non-zero result, so the
assertion is changed from `>` to `>=`.
@github-actions github-actions bot added the cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee label Aug 22, 2024
@flrgh flrgh merged commit 58c580f into master Aug 22, 2024
41 checks passed
@flrgh flrgh deleted the tests/ai-resp-transformer-latency branch August 22, 2024 23:59
github-actions bot pushed a commit that referenced this pull request Aug 23, 2024
The way this latency is measured in the code is not granular enough to
guarantee that it will always produce a non-zero result, so the
assertion is changed from `>` to `>=`.

(cherry picked from commit 58c580f)
@team-gateway-bot
Copy link
Collaborator

Successfully created cherry-pick PR for master:

@team-gateway-bot
Copy link
Collaborator

Successfully created backport PR for release/3.8.x:

bungle pushed a commit that referenced this pull request Aug 23, 2024
The way this latency is measured in the code is not granular enough to
guarantee that it will always produce a non-zero result, so the
assertion is changed from `>` to `>=`.

(cherry picked from commit 58c580f)
curiositycasualty pushed a commit that referenced this pull request Oct 15, 2024
The way this latency is measured in the code is not granular enough to
guarantee that it will always produce a non-zero result, so the
assertion is changed from `>` to `>=`.

(cherry picked from commit 58c580f)

Co-authored-by: Michael Martin <flrgh@protonmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release/3.8.x cherry-pick kong-ee schedule this PR for cherry-picking to kong/kong-ee skip-changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants