[Versioning] Gymnasium 1.0 incompatibility errors

[vmoens]

Stack from ghstack (oldest at bottom):

• -> [Versioning] Gymnasium 1.0 incompatibility errors #2484

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 13 New Failures, 5 Unrelated Failures

As of commit a126b0c with merge base efa5745 ():

NEW FAILURES - The following jobs have failed:

• Continuous Benchmark (PR) / CPU Pytest benchmark (gh)
  /home/runner/work/_temp/9c67eca8-d6f3-4ec6-909a-0a953eb5db7b.sh: line 5: 2113 Bus error (core dumped) $RUN_BENCHMARK /tmp/tmp.mF0IXwhrp7
• Continuous Benchmark (PR) / GPU Pytest benchmark (gh)
  Bus error
• Habitat Tests on Linux / tests (3.9, 12.1) / linux-job (gh)
  RuntimeError: Command docker exec -t 109a4b47717435936a24c64ce68e1ce1a9b5fff875eef495fbd4950b59c69a04 /exec failed with exit code 134
• Libs Tests on Linux / unittests-sklearn (3.9, 12.1) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2484/merge
• Unit-tests on Linux / tests-cpu (3.10) / linux-job (gh)
  RuntimeError: Command docker exec -t 4830b3d6a553a759b706dcbc17cdb3ba2570fd0d1a3663a631221fa0daa3a329 /exec failed with exit code 1
• Unit-tests on Linux / tests-cpu (3.11) / linux-job (gh)
  RuntimeError: Command docker exec -t cb8534a870c2b7e7042615d57f8a69ba2f6dbe1a0b083b8ae19de254de41f90c /exec failed with exit code 1
• Unit-tests on Linux / tests-cpu (3.12) / linux-job (gh)
  RuntimeError: Command docker exec -t 15af970299eb80e67589861afcfe18a216a830b676ac247a410c7b73657423d2 /exec failed with exit code 1
• Unit-tests on Linux / tests-cpu (3.9) / linux-job (gh)
  RuntimeError: Command docker exec -t 659c357d92c118e0593de3c9cfd8ef62ade2e97364e3ac01f9c44b6159c777b8 /exec failed with exit code 1
• Unit-tests on Linux / tests-cpu-oldget (3.12) / linux-job (gh)
  RuntimeError: Command docker exec -t ea8f365358d1328bb027787481198dd055015ba71573a52ef161ae16e127832e /exec failed with exit code 1
• Unit-tests on Linux / tests-gpu (3.11, 12.1) / linux-job (gh)
  RuntimeError: Command docker exec -t 13d698fc65da86bc20058191746fd679d7a2d9d872ed5492dc0f28a632b899de /exec failed with exit code 1
• Unit-tests on Linux / tests-optdeps (3.10, 12.1) / linux-job (gh)
  RuntimeError: Command docker exec -t 79f809ae6fe61fed0f3c47e1f062098dafb5b0a9d84c08febd413830ce0dceed /exec failed with exit code 1
• Unit-tests on Linux / tests-stable-gpu (3.10, 11.8) / linux-job (gh)
  RuntimeError: Command docker exec -t 1101abc8c3d14309dedffd3ff603b2f21cf2d7294a8d9d17ab3beae7893e42cb /exec failed with exit code 1
• Unit-tests on Windows / unittests-cpu / windows-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2484/merge

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 / upload / wheel-py3_9-cpu (gh) (trunk failure)
  ##[error]Unable to find any artifacts for the associated workflow
• Build Windows Wheels / pytorch/rl / upload / wheel-py3_9-cuda11_8 (gh) (trunk failure)
  ##[error]Unable to find any artifacts for the associated workflow
• Build Windows Wheels / pytorch/rl / upload / wheel-py3_9-cuda12_1 (gh) (trunk failure)
  ##[error]Unable to find any artifacts for the associated workflow
• Build Windows Wheels / pytorch/rl / upload / wheel-py3_9-cuda12_4 (gh) (trunk failure)
  ##[error]Unable to find any artifacts for the associated workflow
• Unit-tests on Linux / tests-olddeps (3.8, 11.6) / linux-job (gh) (trunk failure)
  test/test_tensordictmodules.py::TestGRUModule::test_gru_vmap_complex_model

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

[matteobettini]

Suggested change

	* Potential data corruption, as the environment may require/produce garbage data during reset steps.
	* Potential data corruption, as the environment may require/produce invalid data during reset steps.

[matteobettini]

Suggested change

	* Inaccurate step counting, as the auto-reset feature can cause unpredictable numbers of steps to be executed.
	* Inaccurate step counting, the number of step calls to obtain the same amount of data using the autoreset feature will depend on the done frequency of the enviornment.

[matteobettini]

Maybe explain this one too

[matteobettini]

Suggested change

	* Increased computational overhead, as the library would need to handle the additional complexity of auto-resets.
	* Increased computational overhead, as auto-resets introduce additional computational complexity.