rust-lang / rust-lang/rustc_codegen_gcc
Run libgccjit tests in the CI of antoyo/gcc
Open
Nobody has claimed this yet.
libgccjit
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 105
- Avg merge
- 8h 20m
- Merged PRs (30d)
- 14
Description
Perhaps nightly because it will take a lot of time?
Perhaps we could also run the whole test suite as well it happens that I change code outsite of gcc/jit?
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 reviewing the CI configuration for antoyo/gcc and the existing libgccjit tests under gcc/jit. Determine how a nightly run could cover those tests, and whether the whole test suite should also run; done means the selected suites execute reliably in CI without making routine runs impractical.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, compilers, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100