This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients loewis, ncoghlan, nick, vstinner
Date 2013-11-23.14:53:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7ckk3dYHXyS7rAQeDzxqx0=V9Kx6Jty4A9CB=NmKu8xMA@mail.gmail.com>
In-reply-to <1385215561.43.0.644336811927.issue19734@psf.upfronthosting.co.za>
Content
Interesting, looks like the warnings from issue 19694 *weren't* the cause
of the bad return code - something else is failing. I should have some time
to investigate tomorrow afternoon, but it will consist of trying to improve
the diagnostic output from the tests. If we can get the buildbot owners
involved, that could help a lot (1 am here, I'm about to go to sleep).
On 24 Nov 2013 00:06, "STINNER Victor" <report@bugs.python.org> wrote:

>
> STINNER Victor added the comment:
>
> Error similar to Solaris on OpenIndiana:
>
>
> http://buildbot.python.org/all/builders/AMD64%20OpenIndiana%203.x/builds/6946/steps/test/logs/stdio
>
> ======================================================================
> FAIL: test_with_pip (test.test_venv.EnsurePipTest)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File
> "/export/home/buildbot/64bits/3.x.cea-indiana-amd64/build/Lib/test/test_venv.py",
> line 294, in test_with_pip
>     self.assertEqual(err, b"")
> AssertionError: b'/tmp/tmpnv3o61s9/bin/python: No module named pip\n' !=
> b''
>
> ----------------------------------------------------------------------
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue19734>
> _______________________________________
>
History
Date User Action Args
2013-11-23 14:53:06ncoghlansetrecipients: + ncoghlan, loewis, vstinner, nick
2013-11-23 14:53:06ncoghlanlinkissue19734 messages
2013-11-23 14:53:06ncoghlancreate