oasisprotocol / oasisprotocol/oasis-core
CI Job Scheduling
Open
Nobody has claimed this yet.
c:testing
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Some e2e tests right now are being scheduled very inefficiently, increasing the total time it takes to run the whole test suite. If each test had an expected time it takes to run, the scheduling could be made more optimal with some offline processing.
Contributor guide
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 locating the e2e test definitions and CI job scheduling configuration; the issue names no specific files or entry points. Determine how expected test durations could be collected and used by offline scheduling, then verify that the full suite finishes with less scheduling inefficiency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100