Run unsupported platforms anyways, to hopefully improve platform coverage
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 323
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
When a build doesn't eval due to unsupported platform, ofborg could run the build anyways, to see if it would succeed, if this were an allowed platform. In the reporting comment, it should then mention that:
Successfully built on darwin, even though it's not in meta.platforms
or
Failed to build on darwin, in accordance with this platform not being in meta.platforms
(or something along those lines)
This could improve the platform coverage situation.
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 tracing where ofborg evaluates an unsupported platform and where it builds the reporting comment. Determine how an opt-in build should be scheduled and how success or failure should be distinguished from normal supported-platform results, then verify the behavior with the relevant existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100