From b2adb96ec760bb710b2eaa2d635169fad4937a25 Mon Sep 17 00:00:00 2001
From: Charlie Marsh <charlie.r.marsh@gmail.com>
Date: Wed, 8 May 2024 14:04:57 -0400
Subject: [PATCH] Ignore `compile_invalid_pyc_invalidation_mode` on macOS
 (#3465)

## Summary

This is annoying both locally in CI. If anyone wants to fuss with the
filters to fix it, that's fine too, but IMO it's better to disable than
leave it enabled on macOS for now.
---
 crates/uv/tests/pip_sync.rs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/crates/uv/tests/pip_sync.rs b/crates/uv/tests/pip_sync.rs
index fb18eb0d4..fa14e2df5 100644
--- a/crates/uv/tests/pip_sync.rs
+++ b/crates/uv/tests/pip_sync.rs
@@ -3036,6 +3036,7 @@ fn compile() -> Result<()> {
 
 /// Test that the `PYC_INVALIDATION_MODE` option is recognized and that the error handling works.
 #[test]
+#[cfg_attr(macos, ignore = "The bytecode trace is spuriously different on macOS")]
 fn compile_invalid_pyc_invalidation_mode() -> Result<()> {
     let context = TestContext::new("3.12");