-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
bpo-45629: Add a test for the "freeze" tool. #29222
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
bpo-45629: Add a test for the "freeze" tool. #29222
Conversation
🤖 New build scheduled with the buildbot fleet by @ericsnowcurrently for commit f6a8755 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
🤖 New build scheduled with the buildbot fleet by @ericsnowcurrently for commit cc68b86 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
🤖 New build scheduled with the buildbot fleet by @ericsnowcurrently for commit 4b315b0 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
@gpshead you may notice that I'm doing an out-of-tree build. 🙂 |
🤖 New build scheduled with the buildbot fleet by @ericsnowcurrently for commit 4c18103 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
It was added as part of python#29222 to avoid running freeze tool tests on the buildbots but the logic was wrong so it did not skip tests on typical posix setup buildbots where the worker is launched from cron via an @reboot task and thus have no USER environment variable. This uses the canonical `getpass.getuser()` API rather than rolling its own attempt.
It was added as part of #29222 to avoid running freeze tool tests on the buildbots but the logic was wrong so it did not skip tests on typical posix setup buildbots where the worker is launched from cron via an @reboot task and thus have no USER environment variable. This uses the canonical `getpass.getuser()` API rather than rolling its own attempt.
The "freeze" tool has been part of the repo for a long time. However, it hasn't had any tests in the test suite to guard against regressions. We add such a test here. This is especially important as there has been a lot of change recently related to frozen modules, with more to come.
Note that as part of the test we build Python out-of-tree and install it in a temp dir.
https://bugs.python.org/issue45629