[issue24308] Test failure: test_with_pip (test.test_venv.EnsurePipTest in 3.x

2015-06-01 Thread Ned Deily
Ned Deily added the comment: This is covered by Issue24267; let's track it there. -- nosy: +ned.deily resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> test_venv.EnsurePipTest.test_with_pip triggers version check over network _

[issue24308] Test failure: test_with_pip (test.test_venv.EnsurePipTest in 3.x

2015-05-28 Thread Martin Panter
Martin Panter added the comment: Are you sure if fails since those revisions, or is _fixed_ by those revisions? See my initial report in Issue 24267. For me this test started failing a few weeks ago, and was fixed by updating to revision 29b95625a07c (“Merge 3.4 into default, upgrading pip to

[issue24308] Test failure: test_with_pip (test.test_venv.EnsurePipTest in 3.x

2015-05-27 Thread koobs
koobs added the comment: My mistake, revision 1ca30423b0c99c9599d5d4654323eeeae4a03804 or revision 29b95625a07cc5bb22e260c983500ed9efed67bf -- ___ Python tracker ___

[issue24308] Test failure: test_with_pip (test.test_venv.EnsurePipTest in 3.x

2015-05-27 Thread koobs
New submission from koobs: test_with_pip fails since revision 0d0989359bbbff9aa502158e362eb298e1a8ba7c with the following output: == FAIL: test_with_pip (test.test_venv.EnsurePipTest) ---