Fix compilation tests find commands

[ProExpertProg]

Purpose

Compilation tests were using the find command, which does not propagate errors, so the CI passes even when tests fail.

Test Plan

CI (first commit should fail)

---

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

[gemini-code-assist]

Code Review

This pull request fixes an issue with test command execution in the Buildkite pipeline by replacing find -exec with a find | xargs pipe. This correctly propagates pytest exit codes, ensuring that test failures are properly reported. However, the new implementation has a potential issue: if find does not locate any test files, the step will pass silently. This could mask problems in the test suite. I've added suggestions to make these steps fail if no test files are found, which will make the CI pipeline more robust.

[gemini-code-assist]

While this change correctly propagates pytest exit codes, it introduces an issue where the step will silently pass if find doesn't locate any test files. A test step that is expected to run tests should fail if no tests are found to avoid giving a false sense of security. I suggest adding a check to ensure at least one test file is found.

  - |
    set -e -o pipefail
    found_files=$(find compile/ -maxdepth 1 -name 'test_*.py' -print0)
    if [ -z "$found_files" ]; then
      echo "FAIL: No test files found for PyTorch Compile Smoke Test" >&2
      exit 1
    fi
    printf "%s" "$found_files" | xargs -0 -n1 -I{} pytest -s -v "{}"

[gemini-code-assist]

Similar to the previous comment, this change will cause the test step to pass silently if no test files are found. This can mask issues, for example if test files are accidentally moved or renamed. To ensure the CI pipeline is robust, the step should fail if it's expected to run tests but doesn't find any.

  - |
    set -e -o pipefail
    found_files=$(find compile/fullgraph -maxdepth 1 -name 'test_*.py' -not -name 'test_full_graph.py' -print0)
    if [ -z "$found_files" ]; then
      echo "FAIL: No test files found for PyTorch Fullgraph Smoke Test" >&2
      exit 1
    fi
    printf "%s" "$found_files" | xargs -0 -n1 -I{} pytest -s -v "{}"

[ApostaC]

Overall LGTM. Just a quick question: what will happen if there is no file found?