trifectatechfoundation / trifectatechfoundation/sudo-rs
Use release build for compliance tests?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4.5k
- Forks
- 179
- Avg merge
- 16h 45m
- Merged PRs (30d)
- 4
Description
See the discussion at #892
This does require
- using
RUSTFLAGS="-C debug-assertions -C overflow-checks"` at the release side. - using the release Dockerfile to build "sudo under test".
Or can we omit the last step and observe that rustc produces the same binary in both cases?
This wasn't done earlier because the test-framework predates the release build framework.
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 with the discussion in #892, then read the existing test-framework and release-build framework mentioned in the issue. Determine whether compliance tests must use the release Dockerfile and the specified RUSTFLAGS, or whether binary equivalence can be relied on; the work is done when that decision is implemented and the compliance tests run against the agreed build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100