[RELEASE] Branch Cut for Release 0.18.0

[PaliC]

No description provided.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 18 New Failures, 1 Pending, 8 Unrelated Failures

As of commit 1edf1cd with merge base 656a3b4 ():

NEW FAILURES - The following jobs have failed:

• Bandit / build (gh)
  Process completed with exit code 1.
• Build documentation / build / Build doc (gh)
  RuntimeError: Command docker exec -t 62e268d653f67e5e26adbfd20e378b5386b524610262e7b036298e1d332c97a0 /exec failed with exit code 1
• Build Linux Conda / pytorch/text / upload / conda-py3_12-cpu (gh)
  Unable to find an artifact with the name: pytorch_text__3.12_cpu_
• Build M1 Conda / pytorch/text / upload / conda-py3_12-cpu (gh)
  Unable to find an artifact with the name: pytorch_text__3.12_cpu_
• Build Windows Conda / pytorch/text / upload / conda-py3_12-cpu (gh)
  Unable to find an artifact with the name: pytorch_text__3.12_cpu_
• Build Windows Conda / pytorch/text / upload / conda-py3_8-cpu (gh)
  Unable to find any artifacts for the associated workflow
• cron / nightly / validate-binaries / linux-conda-3.8-cpu / linux-conda-3.8-cpu (gh)
  RuntimeError: Command docker exec -t 54ac793590e915526615384c63143498b369bff5729a2990e20111b1e4b379e7 /exec failed with exit code 1
• cron / nightly / validate-binaries / linux-manywheel-3.8-cpu / linux-manywheel-3.8-cpu (gh)
  RuntimeError: Command docker exec -t 72ea2e296b6b7612f275da51b68cf2e231c61b016704872d6ec2842768be674b /exec failed with exit code 1
• cron / nightly / validate-binaries / linux-manywheel-3.8-rocm5.6 / linux-manywheel-3.8-rocm5.6 (gh)
  RuntimeError: Command docker exec -t 760c4641d9d1ec2d33689c7bc7193f5c73a32c7c20dca84b875edd7ab0b554c1 /exec failed with exit code 1
• cron / nightly / validate-binaries / linux-manywheel-3.8-rocm5.7 / linux-manywheel-3.8-rocm5.7 (gh)
  RuntimeError: Command docker exec -t be37f159ed1df6f05af1853a5c0149442c4cd6a7c40f03427f7275dd3de1c4ed /exec failed with exit code 1
• cron / nightly / validate-binaries / windows-conda-3.8-cpu / windows-conda-3.8-cpu (gh)
  Process completed with exit code 1.
• cron / nightly / validate-binaries / windows-wheel-3.8-cpu / windows-wheel-3.8-cpu (gh)
  Process completed with exit code 1.
• Integration Test / tests (3.8) / linux-job (gh)
  RuntimeError: Command docker exec -t 732e8fa8c4c02d097f1ffbe7788a201d3886c2b2985886351715ace5cc58ef00 /exec failed with exit code 1
• Lint / python-source-and-configs / linux-job (gh)
  RuntimeError: Command docker exec -t d17f688fdc8c9bbce04cbaa299bfb32c4156e1bbbd9a7a3ec959b719d2e6fe87 /exec failed with exit code 1
• Unit-tests on Linux CPU / tests (3.10) / linux-job (gh)
  RuntimeError: Command docker exec -t 929fbf8420787c330ce09cb3ec046765572ea31191074571caf59c2a2eedf442 /exec failed with exit code 1
• Unit-tests on Linux CPU / tests (3.8) / linux-job (gh)
  RuntimeError: Command docker exec -t 20f1fc50cb35671df8fd024612aa6b5851600d30a5a739cb74f755d6e9f22e86 /exec failed with exit code 1
• Unit-tests on Linux CPU / tests (3.9) / linux-job (gh)
  RuntimeError: Command docker exec -t d5f96413cf7b1a22bbba9ac30e2b7d0b0be6c23f7442f2dccb67813323efb319 /exec failed with exit code 1
• Unit-tests on Linux GPU / tests (3.8, 11.7) / linux-job (gh)
  RuntimeError: Command docker exec -t df8b17099c35aad8db411657c6114702fc20cbb2becce99d2da4c2f2606704ee /exec failed with exit code 1

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• cron / nightly / validate-binaries / macos-conda-3.8-cpu / macos-arm64-conda-3.8-cpu (gh)
• cron / nightly / validate-binaries / macos-wheel-3.8-cpu / macos-arm64-wheel-3.8-cpu (gh)

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

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

• Build Windows Wheels / pytorch/text / upload / wheel-py3_8-cpu (gh)
  Unable to find any artifacts for the associated workflow
• Unit-tests on Macos CPU / tests (3.10) / macos-job (gh)
  thinc/backends/numpy_ops.cpp:5948:3: error: no member named 'use_tracing' in '_PyCFrame'
• Unit-tests on Macos CPU / tests (3.8) / macos-job (gh)
  thinc/backends/numpy_ops.cpp:5948:3: error: no member named 'use_tracing' in '_PyCFrame'
• Unit-tests on Macos CPU / tests (3.9) / macos-job (gh)
  thinc/backends/numpy_ops.cpp:5948:3: error: no member named 'use_tracing' in '_PyCFrame'
• Unit-tests on Windows CPU / tests (3.8) / windows-job (gh)
  torchtext_unittest\test_build.py::TestDataUtils::test_get_tokenizer_spacy
• Unit-tests on Windows CPU / tests (3.9) / windows-job (gh)
  torchtext_unittest\test_build.py::TestDataUtils::test_get_tokenizer_spacy

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

[atalman]

not required for mian