From 44b7b9a3c1fc23c176dce54c903db469c5e43752 Mon Sep 17 00:00:00 2001 From: Andrew Gallant Date: Mon, 19 Aug 2024 08:41:05 -0400 Subject: [PATCH] uv/tests: tweak marker emitting tests to use Python 3.12.1 The test output seems to depend on using Python 3.12.1 specifically. While I'm not sure how it happens, it seems like these can get out of sync between CI and local testing. In this case, I had a problem where the marker expressions emitted locally were tied to Python 3.12.4, but the tests in CI were tied to Python 3.12.1. Changing the test to require 3.12.1 specifically fixes this. --- crates/uv/tests/pip_compile.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/crates/uv/tests/pip_compile.rs b/crates/uv/tests/pip_compile.rs index c99061622..180f9277c 100644 --- a/crates/uv/tests/pip_compile.rs +++ b/crates/uv/tests/pip_compile.rs @@ -9989,7 +9989,7 @@ fn dynamic_dependencies() -> Result<()> { #[cfg(target_os = "linux")] #[test] fn emit_marker_expression_exciting_linux() -> Result<()> { - let context = TestContext::new("3.12"); + let context = TestContext::new("3.12.1"); let requirements_in = context.temp_dir.child("requirements.in"); requirements_in.write_str("anyio")?; @@ -10026,7 +10026,7 @@ fn emit_marker_expression_exciting_linux() -> Result<()> { #[cfg(target_os = "linux")] #[test] fn emit_marker_expression_direct() -> Result<()> { - let context = TestContext::new("3.12"); + let context = TestContext::new("3.12.1"); let requirements_in = context.temp_dir.child("requirements.in"); requirements_in.write_str("anyio ; sys_platform == 'linux'")?; @@ -10106,7 +10106,7 @@ fn emit_marker_expression_conditional() -> Result<()> { #[cfg(target_os = "linux")] #[test] fn emit_marker_expression_pypy() -> Result<()> { - let context = TestContext::new("3.12"); + let context = TestContext::new("3.12.1"); let requirements_in = context.temp_dir.child("requirements.in"); requirements_in.write_str("pendulum")?;