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

chore: execute performance tests after all other tests have been executed #479

Merged
merged 1 commit into from
Nov 30, 2022

Conversation

bacherfl
Copy link
Member

This PR avoids having multiple instances of the same controller running at the same time during the component/performance tests

Signed-off-by: Florian Bacher [email protected]

@codecov
Copy link

codecov bot commented Nov 30, 2022

Codecov Report

Merging #479 (c57695b) into main (02c2726) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #479   +/-   ##
=======================================
  Coverage   59.40%   59.40%           
=======================================
  Files          28       28           
  Lines        2101     2101           
=======================================
  Hits         1248     1248           
  Misses        747      747           
  Partials      106      106           
Flag Coverage Δ
component-tests 50.12% <ø> (-0.97%) ⬇️
keptn-lifecycle-operator 56.64% <ø> (ø)
scheduler 4.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@bacherfl bacherfl merged commit 145a6ab into keptn:main Nov 30, 2022
@keptn-bot keptn-bot mentioned this pull request Nov 30, 2022
@bacherfl bacherfl deleted the fix/performance-after-other-tests branch November 30, 2022 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants