| Summary: | sys-apps/portage: show a message that some QA test have been skipped due to parallel-install FEATURE | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Pacho Ramos <pacho> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Can we skip the einfo message if the check didn't find anything, or should we show it unconditionally? I'm thinking that we'll need to document these checks in a man page and note the parallel-install caveat there. I would show it fewer times to not pollute too much logs (but still allow user to know that the test is not working properly). I guess this case won't be fixable with bug 725112 , right? :/ These QA checks are just not compatible with parallel-install, since they rely on state of the live filesystem. |
I was wondering about why I wasn't getting the QA warnings about not updating icon/mime cache when needed and I found: # parallel-install makes it impossible to blame a specific package has parallel-install ${FEATURES} && return Maybe it should show an "einfo" statement to show that it's being skipped instead of doing it silently Thanks a lot