Fix pypy3 tests

[benoit-pierre]

The problem was the workaround for pypa/virtualenv#306: using [...]/workspace/venv/lib-python/3.5 as the virtualenv lib directory when [...]/workspace/venv/lib-python/3 is the actual directory used when running with PyPy 3.

[benoit-pierre]

It would be great if the integration tests on Travis were a little bit more verbose: with the full testsuite taking so long, it's annoying to have to wait for it to end to be able to see the name of failed tests.

If switching pytest verbose mode on is too much, maybe use pytest-sugar?:

 tests/functional/test_install.py ⨯✓✓                      15% █▌
 tests/functional/test_hash.py ✓                           16% █▋
 tests/functional/test_install.py ✓✓                       16% █▋
 tests/functional/test_help.py ✓                           16% █▋
 tests/functional/test_install.py ✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓✓s✓     22% ██▎

[benoit-pierre]

I'm getting a failure locally with pypy3, in test_pip_second_command_line_interface_works, but only when run with xdist... ¯\(ツ)/¯

[pradyunsg]

maybe use pytest-sugar?

The issue with that is that the output is extremely long on running with xdist. I'm tempted to write a plugin for this but that's just a thought as of now...

[benoit-pierre]

Fixed lint failures.

[benoit-pierre]

Restarded the pypy/pypy3 jobs because they failed due to timeouts, and the pypy3 job failed again...

[pradyunsg]

I've re-triggered the pypy3 job now -- if it fails, I think someone would need to investigate what's causing the timeouts in more detail.

[pradyunsg]

It seems to me that tests are hitting pytest-dev/pytest#625?

[benoit-pierre]

Yeah, there's definitely something fishy. I've restarted the job multiple times, no luck... It did pass on my repository Travis run, after 49 minutes!

[benoit-pierre]

pytest-dev/pytest-xdist#131

[benoit-pierre]

Rebased.

[pradyunsg]

LGTM on a first pass.

[dstufft]

I think this can be closed now?

[pradyunsg]

Yeah. It got merged as a part of #4706

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.