[JakeStevens]

Summary: Run the backend test suite's cpu_fp32 flow in OSS CI the way XNNPACK, Vulkan and WebGPU run theirs, now that EXECUTORCH_BUILD_CPU builds CpuBackend into the pybindings.

Differential Revision: D127905371

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/24252

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 1 Unrelated Failure, 2 Unclassified Failures

As of commit 1a8bc8c with merge base 616a0b4 ():

NEW FAILURE - The following job has failed:

• Build Presets / apple (macos) / build (gh)
  ##[error]fatal: unable to access 'https://github.com/pybind/pybind11.git/': Failed to connect to github.com port 443 after 754 ms: Couldn't connect to server

UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:

• Test CPU Backend / test-cpu / test-backend-linux (cpu_fp32, models) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  /__w/executorch/executorch/pytorch/executorch/backends/native/runtime/graph/TensorMeta.cpp:21:10: error: no matching function for call to object of type 'const std::ranges::__equal_fn'
• Test CPU Backend / test-cpu / test-backend-linux (cpu_fp32, operators) / linux-job (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
  RuntimeError: Command bash /__w/_temp/exec_script failed with exit code 1

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• Test CoreML Backend / test-coreml / test-backend-macos (coreml, models) / macos-job (gh) (trunk failure)
  ##[error]The operation was canceled.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-codesync]

@JakeStevens has exported this pull request. If you are a Meta employee, you can view the originating Diff in D127905371.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.