oasisprotocol / oasisprotocol/oasis-sdk
ci: ideas for restructuring ci-test
Open
Nobody has claimed this yet.
c:testing
- Dominant language
- Rust
- Stars
- 90
- Forks
- 35
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 5
Description
- the longest running ones are those that compile rust: test-rust, test-rust-sgx, e2e-ts-web-rt, e2e-rt
- we compile multiple runtimes. maybe we could compile those in separate jobs in parallel, and have those jobs upload the runtimes as artifacts
- has rust's compile cache tooling gotten any better since the last time we tried to use it?
- anything that runs a network runs for a few minutes, with the network needing a few epoch transitions to get started. maybe we could run each test that needs a network in a separate job instead of largely in series
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 locating the ci-test workflow and reviewing the test-rust, test-rust-sgx, e2e-ts-web-rt, and e2e-rt jobs. Investigate parallel runtime compilation, artifact sharing, Rust compile-cache tooling, and separate network-dependent jobs; done means a concrete restructuring plan with measurable improvements to build and test time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100