ilmanzo / ilmanzo/BinaryCoverage
implement a 'best effort' install mode
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 9
- Forks
- 6
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 11
Description
As suggested in
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/26253
When given a bunch of binaries to install / wrap , if the 'best effort' option is present do not exit with return code !=0 on any failure, but log the errors.
As I get the original proposal intent, I have mixed feelings on the practice of silencing errors, even when gated with a feature flag.
A similar behavior can be obtained user-side (e.g. on the coverage setup test module) with a loop that instruments one binary at a time , and manage the error result .
Looking for suggestions and feedbacks
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 the code path that handles a batch of binaries to install or wrap, using the linked pull request for the original proposal. Compare it with the loop-based behavior described for the coverage setup test module. Done means failures are logged and the best-effort mode avoids a nonzero result while normal behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- testing, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100