On Sun, 2023-11-26 at 18:33 +0100, Ulrich Mueller wrote:
> > > > > > On Sun, 26 Nov 2023, Michał Górny wrote:
>
> > 3. Forcing `NO_COLOR=1` turns out to cause random test failures,
> > and while fixing them is commendable, it is a pain for arch testing
> > and it is currently blocking
> On Sun, 26 Nov 2023, Michał Górny wrote:
> 3. Forcing `NO_COLOR=1` turns out to cause random test failures,
>and while fixing them is commendable, it is a pain for arch testing
>and it is currently blocking stabilization requests.
I'd argue that test suites that fail because of
Stop implicitly forcing `NO_COLOR` and `NOCOLOR` in ebuild environment.
This is undesired for several reasons:
1. It makes it impossible to control color for emerge output
independently of command output, e.g. when one goes to a pty while
the other goes to logs.
2. It makes it impossible
