Fix flaky `test_optimizations` integration test
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 14
- Forks
- 2
- Avg merge
- 12h 42m
- Merged PRs (30d)
- 61
Description
The test_optimizations integration test in tests/compile_test.rs can be flaky when run in parallel with cargo test. This is because tests might execute concurrently and attempt to access/overwrite the same temporary loop_unroll.mlr_temp_in.mlir file in the current working directory.
To fix this, the test suite should ideally use independent temporary directories for each test case, or name the generated artifacts dynamically based on the test name.
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 with test_optimizations in tests/compile_test.rs and run the integration tests with cargo test in parallel. Trace how loop_unroll.mlr_temp_in.mlir is created and overwritten, then isolate each test's temporary directory or generated artifact name. Done means the tests no longer share that file and pass reliably under parallel execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100