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

Most of the tests in tests/functional/test_install_cleanup.py aren't testing anything #2640

Closed
dstufft opened this issue Apr 7, 2015 · 4 comments · Fixed by #8141
Closed
Labels
auto-locked Outdated issues that have been locked by automation C: tests Testing and related things type: maintenance Related to Development and Maintenance Processes

Comments

@dstufft
Copy link
Member

dstufft commented Apr 7, 2015

Since pip 6 most installations use a randomized build directory, and in pip 7 all installations do unless you specifically mention a directory using --build. However the tests in tests/functional/test_install_cleanup.py assume the old static build directory. We also might not need many of these tests since scripttest ensures there are no tmp dirs left over.

@dstufft dstufft added the C: tests Testing and related things label Mar 22, 2017
@pradyunsg pradyunsg added the type: maintenance Related to Development and Maintenance Processes label Jun 29, 2017
@pradyunsg
Copy link
Member

So, just trim the useless tests correct?

@pradyunsg pradyunsg mentioned this issue Jun 29, 2017
12 tasks
@pradyunsg pradyunsg added this to the Internal Cleansing milestone Jun 6, 2018
@deveshks
Copy link
Contributor

If I understand the issue correctly, there are tests in test_install_cleanup.py, which are using the old static build directory via build = script.venv_path / "build" (e.g here and here etc.

So to address the issue, we would need to remove all such tests. I have made deveshks@b24cbbc to remove those tests.

If the changes are as expected, I can go ahead and create a PR for the same

@pradyunsg
Copy link
Member

@deveshks Yea, that commit looks about right to me. :)

@deveshks
Copy link
Contributor

Yea, that commit looks about right to me. :)

Thanks, I have gone ahead and created a PR for the same

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 24, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation C: tests Testing and related things type: maintenance Related to Development and Maintenance Processes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants