Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest pip release fails #6554

Closed
kerimoyle opened this issue Jan 21, 2020 · 14 comments
Closed

Latest pip release fails #6554

kerimoyle opened this issue Jan 21, 2020 · 14 comments
Labels
Support Support question

Comments

@kerimoyle
Copy link

Details

Expected Result

Build without failing ... :)

Actual Result

Currently all builds are failing because the automatic upgrade (since #4823 ) to pip 20.0 was buggy (see pypa/pip#7620 ). There's now a 20.0.1 release which seems to have fixed the problem for others ... but how can I force my readthedocs to also upgrade to the .1 version?

@stsewd
Copy link
Member

stsewd commented Jan 21, 2020

Hi, you can force a clean installation by wiping the environment https://docs.readthedocs.io/en/stable/guides/wipe-environment.html

That will download the latest pip instead of using one from cache

@stsewd stsewd closed this as completed Jan 21, 2020
@stsewd stsewd added the Support Support question label Jan 21, 2020
@kerimoyle
Copy link
Author

Brilliant - thanks so much for the quick reply :)

@Aricg
Copy link

Aricg commented Jan 22, 2020

Hi,
Wiping master or latest only fixes this for me for a single build, the next one fails with the same error.
All builds are triggered via the v3 api.

ImportError: cannot import name 'PackageFinder' from 'pip._internal.index' (/home/docs/checkouts/readthedocs.org/user_builds/o-ran-sc-doc/envs/master/lib/python3.7/site-packages/pip/_internal/index/__init__.py)

https://readthedocs.org/projects/o-ran-sc-doc/builds/

@stsewd
Copy link
Member

stsewd commented Jan 22, 2020

@Aricg that's weird. Did you wipe only once? I can think of a reason where the wipe didn't propagate to all servers.

@Aricg
Copy link

Aricg commented Jan 22, 2020

@stsewd I have done it multiple times to both stable and master to try to make it "take"
in each case, it only "takes" once.

@stsewd
Copy link
Member

stsewd commented Jan 22, 2020

@Aricg can you please trigger a wipe for latest but don't trigger any build. I want to check the servers for something

@stsewd
Copy link
Member

stsewd commented Jan 22, 2020

@Aricg I just did it by myself from the admin. I think I found the problem #6571

@peterjc
Copy link

peterjc commented Jan 23, 2020

Like @Aricg in the last day or so I have tried wipe only for the problem to recur:
https://readthedocs.org/projects/thapbi-pict/builds/

It looks like the fix for #6571 was merged about 25 minutes ago, so hopefully the fix will go live shortly.

@stsewd
Copy link
Member

stsewd commented Jan 23, 2020

@peterjc probably it will be live next week

@peterjc
Copy link

peterjc commented Jan 23, 2020

Thanks - I'll do a manual wipe as needed until then.

@johannfaouzi
Copy link

Is it possible to do a manual wipe for pull requests? I can't find a way to do so.

@humitos
Copy link
Member

humitos commented Jan 25, 2020

@johannfaouzi currently, no. We don't support that yet.

@SchoolGuy
Copy link

This is breaking this PR cobbler/cobbler#2254

The build environment cannot be wiped because this is (at least to my knowledge) not possible on PR's.

@stsewd
Copy link
Member

stsewd commented Jan 28, 2020

@SchoolGuy see #6566

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Support Support question
Projects
None yet
Development

No branches or pull requests

7 participants