[Algorithm] Update scripts with compile

[vmoens]

Stack from ghstack (oldest at bottom):

• (to be filled)

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 14 New Failures, 9 Unrelated Failures

As of commit 550b423 with merge base e294c68 ():

NEW FAILURES - The following jobs have failed:

• Examples Tests on Linux / tests (3.9, 12.1) / linux-job (gh)
  AttributeError: 'bool' object has no attribute 'any'
• Habitat Tests on Linux / tests (3.9, 12.1) / linux-job (gh)
  RuntimeError: Command docker exec -t 98304cabb3a9a2483eae54a4dbbc6d537836c31acac496ce914c56a9a8a42ec6 /exec failed with exit code 134
• Lint / python-source-and-configs / linux-job (gh)
  torchrl/objectives/value/advantages.py:659:9: F841 local variable 'device' is assigned to but never used
• Unit-tests on Linux / tests-cpu (3.10) / linux-job (gh)
  test/test_transforms.py::TestKLRewardTransform::test_kl_lstm
• Unit-tests on Linux / tests-cpu (3.11) / linux-job (gh)
  test/test_transforms.py::TestKLRewardTransform::test_kl_lstm
• Unit-tests on Linux / tests-cpu (3.12) / linux-job (gh)
  test/test_transforms.py::TestKLRewardTransform::test_kl_lstm
• Unit-tests on Linux / tests-cpu (3.9) / linux-job (gh)
  test/test_transforms.py::TestKLRewardTransform::test_kl_lstm
• Unit-tests on Linux / tests-cpu-oldget (3.12) / linux-job (gh)
  test/test_transforms.py::TestKLRewardTransform::test_kl_lstm
• Unit-tests on Linux / tests-gpu (3.11, 12.1) / linux-job (gh)
  test/test_transforms.py::TestKLRewardTransform::test_kl_lstm
• Unit-tests on Linux / tests-olddeps (3.8, 11.6) / linux-job (gh)
  RuntimeError: Command docker exec -t 76f14578a4598a5ded3526337d439d6d489a6e3182417421a59d73adb81e97b1 /exec failed with exit code 1
• Unit-tests on Linux / tests-optdeps (3.10, 12.1) / linux-job (gh)
  test/test_transforms.py::TestKLRewardTransform::test_kl_lstm
• Unit-tests on Linux / tests-stable-gpu (3.10, 11.8) / linux-job (gh)
  test/test_transforms.py::TestKLRewardTransform::test_kl_lstm
• Unit-tests on Windows / unittests-cpu / windows-job (gh)
  test/test_transforms.py::TestKLRewardTransform::test_kl_lstm
• Wheels / build-wheel-windows (3.10, 3.10.3) (gh)

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

• Continuous Benchmark (PR) / CPU Pytest benchmark (gh) (detected as infra flaky with no log or failing log classifier)
• Continuous Benchmark (PR) / GPU Pytest benchmark (gh) (detected as infra flaky with no log or failing log classifier)

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/rl (pytorch/rl, .github/scripts/td_script.sh, .github/scripts/version_script.bat, python ... / upload / wheel-py3_9-cpu (gh) (trunk failure)
• Build Windows Wheels / pytorch/rl (pytorch/rl, .github/scripts/td_script.sh, .github/scripts/version_script.bat, python ... / upload / wheel-py3_9-cuda11_8 (gh) (trunk failure)
• Build Windows Wheels / pytorch/rl (pytorch/rl, .github/scripts/td_script.sh, .github/scripts/version_script.bat, python ... / upload / wheel-py3_9-cuda12_1 (gh) (trunk failure)
• Build Windows Wheels / pytorch/rl (pytorch/rl, .github/scripts/td_script.sh, .github/scripts/version_script.bat, python ... / upload / wheel-py3_9-cuda12_4 (gh) (trunk failure)
• Wheels / build-wheel-windows (3.11, 3.11) (gh) (trunk failure)
• Wheels / build-wheel-windows (3.12, 3.12) (gh) (trunk failure)
• Wheels / build-wheel-windows (3.9, 3.9) (gh) (trunk failure)

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

[facebook-github-bot]

Hi @vmoens!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!