-
Notifications
You must be signed in to change notification settings - Fork 135
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
Improve isolation of tests for flit install
#609
Comments
The tests are all failing with
This seems to be a problem with your system and not a problem with the tests. |
Yep .. and question ios why test wiote is truing to install something? |
The test filename is:
That should provide a hint for why its trying to install something. Flit has a |
Closing this since this is an environment configuration issue. |
Actually, I think there is a genuine issue with the tests here that we hadn't spotted. The tests do some monkeypatching to redirect installation to temporary directories: Lines 25 to 30 in f5704ea
But this doesn't affect the Lines 152 to 154 in f5704ea
And of course the monkeypatching also won't affect pip when the install code runs that as a subprocess. So I'm going to reopen this 😉 . I'm not sure yet exactly what's the best way to properly isolate those tests - maybe we have to set up a venv for each test, even if that's slower - but I think they do need some work. |
flit install
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulesHere is pytest output:
Here is list of installed modules in build env
The text was updated successfully, but these errors were encountered: