From 15450e64a6a9dacaebf837b6e81b7c8b33780483 Mon Sep 17 00:00:00 2001 From: Dunbobbin Date: Tue, 15 Jul 2025 18:32:01 +0100 Subject: [PATCH] [DTLTO][TEST] Fix Clang driver test failing on some build bots Not all builds name the compiler executable `clang`. For example, the Fuchsia build bots use `llvm` as the executable name, as they combine everything together in a busybot-style binary. Update the Clang driver test to simply check that a non-empty path is provided for the `--thinlto-remote-compiler` argument, rather than hardcoding the executable name. The cross-project test will verify that the path is valid later. Should fix #147265. --- clang/test/Driver/DTLTO/dtlto.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/clang/test/Driver/DTLTO/dtlto.c b/clang/test/Driver/DTLTO/dtlto.c index d72e487e706b2..96795d9a4e6a4 100644 --- a/clang/test/Driver/DTLTO/dtlto.c +++ b/clang/test/Driver/DTLTO/dtlto.c @@ -10,7 +10,7 @@ // FORWARD: ld.lld // FORWARD-SAME: "--thinlto-distributor=d.exe" -// FORWARD-SAME: "--thinlto-remote-compiler={{.*}}clang{{[^\"]*}}" +// FORWARD-SAME: "--thinlto-remote-compiler={{[^"]+}}" // FORWARD-SAME: "--thinlto-distributor-arg=a1" // FORWARD-SAME: "--thinlto-distributor-arg=a2" // FORWARD-SAME: "--thinlto-distributor-arg=a3"