From 6ec407a053293fa748c1e6dbc982f46b3daf9919 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Rodr=C3=ADguez?= Date: Wed, 1 Oct 2025 13:03:39 -0700 Subject: [PATCH] [test] Allow custom conditions for non-standard compilations If someone has configured their build to add some vendor macro, for example, the vendor macro will appear in `customConditions`, which will make the test fail. Modify the test slightly to check for `customConditions` containing `SOMETHING`, instead of only being `SOMETHING` and nothing else. This should still allow the test to pass in Swift CI, but allows vendor macros to work too. --- test/Frontend/print-static-build-config.swift | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/Frontend/print-static-build-config.swift b/test/Frontend/print-static-build-config.swift index 70ac0c9a12fb4..07ad1f9c72fea 100644 --- a/test/Frontend/print-static-build-config.swift +++ b/test/Frontend/print-static-build-config.swift @@ -4,7 +4,7 @@ // CHECK: "attributes": // CHECK-SAME: "escaping" -// CHECK-SAME: "customConditions":["SOMETHING"] +// CHECK-SAME: "customConditions":[{{.*"SOMETHING"[^]]*\]}} // CHECK-SAME: "features": // CHECK-SAME: "AttachedMacros"