[PATCH] tests: redirect virtualenv stderr to same file as stdout
Augie Fackler
raf at durin42.com
Tue Jun 20 21:30:47 UTC 2017
> On Jun 20, 2017, at 17:26, Danek Duvall <danek.duvall at oracle.com> wrote:
>
> Danek Duvall wrote:
>
>> Augie Fackler wrote:
>>
>>>
>>>> On Jun 20, 2017, at 16:53, Augie Fackler <raf at durin42.com> wrote:
>>>>
>>>> # HG changeset patch
>>>> # User Augie Fackler <augie at google.com>
>>>> # Date 1497991974 14400
>>>> # Tue Jun 20 16:52:54 2017 -0400
>>>> # Node ID ff3964f237d601e7c375c10fbf93029b5db39307
>>>> # Parent 0ce2cbebd74964ffe61e79de8941461bccc9371b
>>>> tests: redirect virtualenv stderr to same file as stdout
>>>>
>>>> I'm seeing some failures on the Solaris buildbots due to a warning
>>>> about an old pip, but I can't reproduce this locally. Hopefully this helps.
>>>
>>> Specifically, this is for https://buildbot.mercurial-scm.org/builders/Solaris%2012%20x86%20tests/builds/204/steps/run-tests.py%20%28python%202.7.13%29/logs/stdio - I think I got it right, but I honestly have no idea. Can you check and see if this fixes that test on that machine?
>>
>> I think the 2>&1 would need to be on the subsequent pip install command,
>> but I'll make sure.
>
> Indeed, that's correct.
>
> But assuming that all necessary versions of pip have it, there's also the
> --disable-pip-version-check flag, or --no-index, which implies it. I just
> ran a test (as myself, not in the same environment as the tests), and
> --no-index makes the message go away, as well as lets the test succeed
> without redirecting stderr.
Ooh, nice. If you send that patch CC me and I'll test it and hopefully land it. Nice eye!
>
> Danek
More information about the Mercurial-devel
mailing list