| 1 |
On 12/05/2011 08:07 AM, Mike Frysinger wrote: |
| 2 |
> On Monday 05 December 2011 01:48:34 Zac Medico wrote: |
| 3 |
>> On 12/04/2011 10:48 PM, Mike Frysinger wrote: |
| 4 |
>>> all "failures" that don't result in an aborted build (e.g. EAPI=0 dodoc |
| 5 |
>>> on missing file) will get "missed". many of those are logged as QA |
| 6 |
>>> warnings, but it seems default --quiet-build=y will not include these in |
| 7 |
>>> the log summary. this might be useful to fix -- i'll poke Zac about it |
| 8 |
>>> if he doesn't see this e- mail. |
| 9 |
>> |
| 10 |
>> This is due to the default PORTAGE_ELOG_CLASSES="log warn error" in |
| 11 |
>> make.globals. The developer profile sets |
| 12 |
>> |
| 13 |
>> :PORTAGE_ELOG_CLASSES="${PORTAGE_ELOG_CLASSES} qa", so anyone running |
| 14 |
>> |
| 15 |
>> that profile gets the QA warnings automatically. |
| 16 |
>> |
| 17 |
>> Maybe it would be fine to enable the QA warnings by default for all |
| 18 |
>> users. I don't feel strongly either way. |
| 19 |
> |
| 20 |
> hrm. there's some QA messages i think we should have all our users see by |
| 21 |
> default (so they'll report bugs), and there's some i think should be in the |
| 22 |
> developer profiles. although, i think most are in the former category, so |
| 23 |
> maybe we shouldn't sweat it for now ? |
| 24 |
|
| 25 |
Yeah, I don't think it's a major problem. Developers should be setting |
| 26 |
PORTAGE_ELOG_CLASSES="${PORTAGE_ELOG_CLASSES} qa" manually if they don't |
| 27 |
use the developer profile. |
| 28 |
|
| 29 |
> specifically, i'm thinking of the build type warnings that we label as upstream |
| 30 |
> should be shown to devs and not users ... |
| 31 |
|
| 32 |
We could migrate to ewarn instead of eqawarn for the ones that we want |
| 33 |
all users to see by default. Alternatively, we could introduce a new log |
| 34 |
level, but that seems redundant. |
| 35 |
-- |
| 36 |
Thanks, |
| 37 |
Zac |
Archives