[PrivateUse1] Impl isBuilt() and isAvailable()

[shink]

Follow-up: #146098

cc: @albanD @FFFrog

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

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

✅ You can merge normally! (7 Unrelated Failures)

As of commit 4ff5657 with merge base 103bf64 ():

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

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

• linux-binary-libtorch-release / libtorch-cpu-shared-with-deps-release-build / build (gh) (trunk failure)
  Process completed with exit code 1.
• linux-binary-manywheel / manywheel-py3_9-cuda11_8-build / build (gh) (trunk failure)
  Process completed with exit code 1.
• linux-binary-manywheel / manywheel-py3_9-cuda12_6-build / build (gh) (trunk failure)
  Process completed with exit code 1.
• linux-binary-manywheel / manywheel-py3_9-cuda12_8-build / build (gh) (trunk failure)
  Process completed with exit code 1.
• pull / linux-jammy-py3.9-gcc11 / test (backwards_compat, 1, 1, ephemeral.linux.2xlarge) (gh) (trunk failure)
  test_modules_can_be_imported

UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:

• pull / cuda12.4-py3.10-gcc9-sm75 / test (pr_time_benchmarks, 1, 1, linux.g4dn.metal.nvidia.gpu) (gh) (#149370)
  REGRESSION: benchmark ('aotdispatcher_partitioner_cpu2', 'compile_time_instruction_count') failed, actual result 1744167633 is 1.64% higher than expected 1716000000 ±+1.50% if this is an expected regression, please update the expected results.
• pull / unstable-linux-focal-cuda12.6-py3.10-gcc11-sm89-xfail / build (gh)
  ninja: build stopped: subcommand failed

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

[shink]

@pytorchbot label "topic: not user facing"

[shink]

@albanD Could you please help review this? Thanks!

[shink]

@pytorchbot rebase -b main

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

[pytorchmergebot]

Successfully rebased fix/pu1/hooks onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via git checkout fix/pu1/hooks && git pull --rebase)

[albanD]

Thanks!

[albanD]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

Merge failed

Reason: 2 jobs have failed, first few of them are: linux-binary-manywheel / manywheel-py3_9-cuda12_6-build / build, linux-binary-manywheel / manywheel-py3_9-cuda11_8-build / build

Details for Dev Infra team

Raised by workflow job

[cyyever]

@pytorchbot merge -i

[pytorchmergebot]

Merge started

Your change will be merged while ignoring the following 7 checks: pull / unstable-linux-focal-cuda12.6-py3.10-gcc11-sm89-xfail / build, pull / linux-jammy-py3.9-gcc11 / test (backwards_compat, 1, 1, ephemeral.linux.2xlarge), pull / cuda12.4-py3.10-gcc9-sm75 / test (pr_time_benchmarks, 1, 1, linux.g4dn.metal.nvidia.gpu), linux-binary-libtorch-release / libtorch-cpu-shared-with-deps-release-build / build, linux-binary-manywheel / manywheel-py3_9-cuda12_6-build / build, linux-binary-manywheel / manywheel-py3_9-cuda11_8-build / build, linux-binary-manywheel / manywheel-py3_9-cuda12_8-build / build

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here