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

Regression testing on a scheduled duration #6969

Open
khrm opened this issue Jul 25, 2023 · 3 comments
Open

Regression testing on a scheduled duration #6969

khrm opened this issue Jul 25, 2023 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@khrm
Copy link
Contributor

khrm commented Jul 25, 2023

Feature request

We should have regression tests running on a scheduled duration to detect performance degradation or some other regression issues. Running per pr might be too heavy, so running daily or weekly basis is fine.

Use case

@khrm khrm added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 25, 2023
@afrittoli
Copy link
Member

See related issues:

This would be great to have - it only needs someone to drive the implementation :)
We cannot only run a test before the release though, so we need to:

  • run the tests on a regular basis to have a baseline
  • monitor the results to detect persisting degradations from the baseline

@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 23, 2023
@vdemeester
Copy link
Member

/lifecycle frozen

@tekton-robot tekton-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

4 participants