The Android CI prints unrelated things to stdout, ruining check-run-results tests.
Open
Nobody has claimed this yet.
A-CI
A-meta
O-android
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
See https://github.com/rust-lang/rust/pull/127003#issuecomment-2236125625
uploaded "$TEST_BUILD_DIR/path/to/test/a", waiting for result
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 check-run-results tests and the Android CI discussion linked from the issue, especially the referenced pull request comment. Trace where the unrelated upload message reaches stdout; done means the check-run-results tests receive only expected output and pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, rust
- Domain
- ci-cd, mobile-dev, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100