Re-enable CPU Pytest benchmark job

[ZainRizvi]

Re-enabling the CPU pytest benchmark job. Even though it's failing, the signal is still helpful.

Description

Re-enables the job

Motivation and Context

The signals are useful for the development team and having it hidden will make tracking down issues harder during release.

• I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes

What types of changes does your code introduce? Remove all that do not apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds core functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (update in the documentation)
• Example (update in the folder of examples)

Checklist

Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

• I have read the CONTRIBUTION guide (required)
• My change requires a change to the documentation.
• I have updated the tests accordingly (required for a bug fix or a new feature).
• I have updated the documentation accordingly.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 5 New Failures, 14 Unrelated Failures

As of commit 9876697 with merge base f287bb3 ():

NEW FAILURES - The following jobs have failed:

• Build M1 Wheels / pytorch/rl / build-wheel-py3_9-cpu (gh)
  Process completed with exit code 1.
• Build M1 Wheels / pytorch/rl / upload / upload-wheel-py3_9-cpu (gh)
  Unable to download artifact(s): Artifact not found for name: pytorch_rl__3.9_cpu_
• Continuous Benchmark (PR) / CPU Pytest benchmark (gh)
  Exit code 125 returned from process: file name '/usr/bin/docker', arguments 'create --name 82035b411c1c4a4abce964a2cd3967d2_nvidiacuda1241cudnnruntimeubuntu2204_10015b --label 3a6fb9 --workdir /__w/rl/rl --network github_network_f5ee60f03a04453b8626495c74b3fc31 --cpus all -e "HOME=/github/home" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/ec2-user/actions-runner/_work":"/__w" -v "/home/ec2-user/actions-runner/externals":"/__e":ro -v "/home/ec2-user/actions-runner/_work/_temp":"/__w/_temp" -v "/home/ec2-user/actions-runner/_work/_actions":"/__w/_actions" -v "/home/ec2-user/actions-runner/_work/_tool":"/__w/_tool" -v "/home/ec2-user/actions-runner/_work/_temp/_github_home":"/github/home" -v "/home/ec2-user/actions-runner/_work/_temp/_github_workflow":"/github/workflow" --entrypoint "tail" nvidia/cuda:12.4.1-cudnn-runtime-ubuntu22.04 "-f" "/dev/null"'.
• Habitat Tests on Linux / tests (3.9, 12.8) / linux-job (gh)
  RuntimeError: Command docker exec -t 2eccb2a779c6eb34b44b73ddc8adde5640929824763fa3bcf5275f706c6cd3b9 /exec failed with exit code 1
• Lint / python-source-and-configs / linux-job (gh)
  RuntimeError: Command docker exec -t f61dc071f0132b1bb756a8000cf80a8db037b4c5fdd9d099747f6a971f4dbd98 /exec failed with exit code 1

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• Continuous Benchmark (PR) / GPU Pytest benchmark (gh) (similar failure)
  RuntimeError: PassManager::run failed

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

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

• Continuous Benchmark / CPU Pytest benchmark (gh) (trunk failure)
• Continuous Benchmark / GPU Pytest benchmark (gh) (trunk failure)
  RuntimeError: PassManager::run failed
• Libs Tests on Linux / unittests-gym (3.9, 12.8) / linux-job (gh) (trunk failure)
  test/test_libs.py::TestGym::test_gym_fake_td[True-False-3-HalfCheetah-v2]
• LLM Tests on Linux / unittests (3.9, 12.8) / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• Unit-tests on Linux / tests-cpu (3.10) / linux-job (gh) (trunk failure)
  test/test_transforms.py::TestDeviceCastTransformWhole::test_transform_rb[LazyTensorStorage-ReplayBuffer]
• Unit-tests on Linux / tests-cpu (3.11) / linux-job (gh) (trunk failure)
  test/test_transforms.py::TestDeviceCastTransformWhole::test_transform_rb[LazyTensorStorage-ReplayBuffer]
• Unit-tests on Linux / tests-cpu (3.12) / linux-job (gh) (trunk failure)
  test/test_transforms.py::TestDeviceCastTransformWhole::test_transform_rb[LazyTensorStorage-ReplayBuffer]
• Unit-tests on Linux / tests-cpu (3.9) / linux-job (gh) (trunk failure)
  test/test_transforms.py::TestDeviceCastTransformWhole::test_transform_rb[LazyTensorStorage-ReplayBuffer]
• Unit-tests on Linux / tests-gpu (3.11, 12.8) / linux-job (gh) (trunk failure)
  test/test_transforms.py::TestDeviceCastTransformWhole::test_transform_rb[LazyTensorStorage-ReplayBuffer]
• Unit-tests on Linux / tests-olddeps (3.9, 11.6) / linux-job (gh) (trunk failure)
  test/test_transforms.py::TestActionDiscretizer::test_transform_env[pendulum-SamplingStrategy.RANDOM-False-True]
• Unit-tests on Linux / tests-optdeps (3.11, 12.8) / linux-job (gh) (trunk failure)
  test/test_transforms.py::TestDeviceCastTransformWhole::test_transform_rb[LazyTensorStorage-ReplayBuffer]
• Unit-tests on Linux / tests-stable-gpu (3.10, 11.8) / linux-job (gh) (trunk failure)
  test/test_transforms.py::TestDeviceCastTransformWhole::test_transform_rb[LazyTensorStorage-ReplayBuffer]
• Unit-tests on Windows / unittests-cpu (3.10, windows.4xlarge, cpu) / windows-job (gh) (trunk failure)
  Process completed with exit code 2.

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

[vmoens]

LGTM
I'll try to fix these CIs asap