Run perf tests on demand
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 43
- Forks
- 17
- Avg merge
- 28m
- Merged PRs (30d)
- 2
Description
After #364, perf tests length is ~1h10m. One must wait till perf tests succeed each time to get an ok from test CI workflow. On the other hand, we don't really monitor performance changes on each patch (and maybe won't ever do since GitHub runners are small virtual machines, not suited for performance tests). It makes sense to run them only with specific label or on a workflow dispatch trigger.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the CI workflow that currently runs the approximately 1-hour-10-minute performance tests and identify its existing triggers and required status checks. Configure the workflow so performance tests run only through the requested label or manual dispatch path, while the normal test workflow can complete without them; verify both trigger paths and the resulting CI status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, lua
- Domain
- ci-cd, performance, testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100