From fb5b8c36534d25232ef53936ee1dec5321471ad8 Mon Sep 17 00:00:00 2001
From: Brent Westbrook <36778786+ntBre@users.noreply.github.com>
Date: Sat, 15 Nov 2025 13:12:10 -0500
Subject: [PATCH] Fix default test executable in py-fuzzer (#21468)

Summary
--

I was firing up the fuzzer tonight and hit an assertion error here. We
now build with the `profiling` profile, so we need to use that
executable too.

This hasn't affected CI because we always set the `--test-executable`.

Test Plan
--

Ran the script again with the same arguments on this branch
---
 python/py-fuzzer/fuzz.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/python/py-fuzzer/fuzz.py b/python/py-fuzzer/fuzz.py
index 035838a6d1..090f329b32 100644
--- a/python/py-fuzzer/fuzz.py
+++ b/python/py-fuzzer/fuzz.py
@@ -414,7 +414,7 @@ def parse_args() -> ResolvedCliArgs:
         except subprocess.CalledProcessError as e:
             print(e.stderr)
             raise
-        args.test_executable = Path("target", "release", executable)
+        args.test_executable = Path("target", "profiling", executable)
         assert args.test_executable.is_file()
 
     seed_arguments: list[range | int] = args.seeds