Repository navigation
Add regression test for uv#23284 - #3135
astral-automations-bot[bot] wants to merge 1 commit into
Conversation
| /// When DNS resolution fails while opening an HTTPS tunnel, the error names only the index, | ||
| /// not the failing proxy host (astral-sh/uv#23284). | ||
| /// An overlong DNS label makes glibc reject the proxy host without a DNS lookup. | ||
| #[cfg(all(feature = "test-python", target_os = "linux", target_env = "gnu"))] |
There was a problem hiding this comment.
[P3] Run the proxy DNS reproductions on Linux musl too
Both tests skip musl, the target reported in astral-sh#23284. The 64-byte label also fails before a DNS query on musl; its final error reads Name does not resolve rather than glibc’s Name or service not known. Allow both Linux targets and normalize just those two messages with a snapshot filter. That keeps the proxy hostname and the HTTPS-only tunnel cause visible, which are the parts these tests need to distinguish.
| let context = uv_test::test_context_with_versions!(&["3.14"]); | ||
| let pyproject_toml = context.temp_dir.child("pyproject.toml"); | ||
| pyproject_toml.write_str(indoc! {r#" |
There was a problem hiding this comment.
[P3] Exercise the proxy failure without a project fixture
Both tests write a pyproject.toml and snapshot Python 3.14 selection, but neither is needed to trigger the failure. I reproduced both cause chains with uv pip install on Python 3.12, including the extra tunnel cause for HTTPS. Following the neighboring connect_timeout_index pattern—test_context!("3.12") and context.pip_install().arg("iniconfig")—would remove both manifests and keep the snapshots focused on the network diagnostic.
Add a minimal integration test that reproduces astral-sh#23284.