compiletest: investigate if it's possible to do run-time capability detection against *target*
Open
Nobody has claimed this yet.
A-compiletest
A-cross
C-enhancement
E-hard
E-needs-design
T-bootstrap
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Some tests are conditioned on capabilities, which are most accurately detected at run-time against the target under cross-compilation scenarios (compared to having to maintain allowlists or denylists of targets). However, implementing this is non-trivial:
- You have to build and run the capability run-time test as an executable on the target, not the host. This may involve having to work with custom test runners (e.g.
wasmtime) or remote-test-server. - The target may not support std!
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 tracing compiletest's capability-conditioned tests and how cross-compilation currently selects capabilities. Investigate the target-side execution constraints, including custom runners such as wasmtime and remote-test-server, as well as targets without std!. Done means documenting whether runtime detection is feasible and what design constraints or alternatives remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100