As suggested in
os-autoinst/os-autoinst-distri-opensuse#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
As suggested in
os-autoinst/os-autoinst-distri-opensuse#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