pip cache collisions

[JackLeo]

• Pip version: 10.0.1
• Python version: Python 2.7.5
• Operating system: Centos 7

Description:

In our CI server, we are running parallel stages that create their own virtual environments and install dependencies. Once in a while, it returns that something is missing and two stages fail at the time. I've replicated the problem with just 3 parallel stages. This problem emerged after warehouse release.

What I've run:

Each stage follows the same setup:

virtualenv env
./bin/pip install -r requirements.txt # file with +10 dependencies with locked versions

...
Collecting nose-timer==0.6.0 (from -r requirements.txt (line 50))
Collecting nose-xunitmp==0.4.0 (from -r requirements.txt (line 51))
Collecting nose==1.3.7 (from -r requirements.txt (line 52))
Could not find a version that satisfies the requirement nose==1.3.7 (from -r requirements.txt (line 52)) (from versions: )

No matching distribution found for nose==1.3.7 (from -r requirements.txt (line 52))

script returned exit code 1

And the other stage

...
Collecting mock==2.0.0 (from -r requirements.txt (line 49))

  Using cached https://files.pythonhosted.org/packages/e6/35/f187bdf23be87092bd0f1200d43d23076cee4d0dec109f195173fd3ebc79/mock-2.0.0-py2.py3-none-any.whl

Collecting nose-timer==0.6.0 (from -r requirements.txt (line 50))

Collecting nose-xunitmp==0.4.0 (from -r requirements.txt (line 51))

  Could not find a version that satisfies the requirement nose-xunitmp==0.4.0 (from -r requirements.txt (line 51)) (from versions: )

No matching distribution found for nose-xunitmp==0.4.0 (from -r requirements.txt (line 51))

script returned exit code 1

[njsmith]

This looks like the same (mysterious) issue as pypi/warehouse#3826

[njsmith]

Shoot, I meant #5345. Though that warehouse thing might also be related, it's not clear.

[JackLeo]

Yep, it's the same issue. Should I close this duplicate?

[pradyunsg]

Should I close this duplicate?

Yep. I'll do it.

[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.