-
Notifications
You must be signed in to change notification settings - Fork 900
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
Certain tests & scenarios are sensitive to exported environment variables #9873
Comments
Thank you for filing this! I'm very supportive of ensuring these are cleared in the test suite. The exception is |
For my particular case, clearing these variables across the board would mean that the tests will fail to reach out over the network (there's a MITM proxy that rewrites certificates, so the HTTPS stuff will fail with a TLS errors). There might be multiple smaller fixes needed here:
OTOH, I should check whether using a user-level configuration file in this environment keeps things functional though. I'll dig a bit more next week -- I don't wanna be touching $work devices over the weekend. 😅 |
This is a very annoying Clap behavior, afaik. I've been meaning to file an issue for that. |
(We should probably omit |
## Summary I also omitted `--no-progress` (we omit `--verbose` and `--quiet` -- this seems similar). Part of: #9873.
[context: I'm working on #9849, and a few tests are failing for me due to issues related to the network-related environment variables]
When certain environment variables are set, uv's tests end up failing for various reasons. I've listed a few of the relevant scenarios below... It would be good to have uv's tests be less fragile to configuration settings that might need to be modified due to the network configuration.
A few of the test failures, hidden in a details tag
The
usage
line of various commands includes the option representation equivalent to the configuration variable (eg: withUV_NATIVE_TLS=true
).The warning about indexes being specified not persisting in
pyproject.toml
causes many tests to fail, even when the configured index URL is done asUV_INDEX_URL=https://pypi.org/simple
(which should functionally be a no-op).Certain scenarios fail when
UV_INDEX_URL=https://pypi.org/simple/
is set, since there's a mismatch between trailing slash vs no trailing slash.The settings-related tests expect a clean environment:
The text was updated successfully, but these errors were encountered: