PLSysSec / PLSysSec/cargo-scan
Nondeterministic output on test crates
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 47
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
The output on test crates (make test) seems to be nondeterministically adding or removing a few lines, particularly on dependency-ex, see the bot updates from CI:
The only thing that changed between the two was cargo fmt so I don't think the actual output should change. It may not be possible to replicate exactly bc the bot is running on Ubuntu (elk is Arch Linux), but we should look into what is happening here.
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 running make test for dependency-ex and compare the outputs from the two linked CI bot updates, noting the Ubuntu versus Arch Linux environments. Check whether cargo fmt alone can affect the generated output; done means the test-crate output is deterministic and the environmental cause is accounted for.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100