[Minor] Fix test_compose_action_spec

[louisfaury]

Description

The last line of the test was always checking to true:

assert "action_2"

and was missing a few characters to be complete:

assert "action_2" in action

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/2493

• 📄 Preview Python docs built from this PR

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

❌ 4 New Failures, 7 Unrelated Failures

As of commit ea2b14f with merge base ec04c35 ():

NEW FAILURES - The following jobs have failed:

• Continuous Benchmark (PR) / CPU Pytest benchmark (gh)
  /home/runner/work/_temp/d7478c2f-27ea-4128-9aaa-ff311da7a762.sh: line 5: 2058 Bus error (core dumped) $RUN_BENCHMARK /tmp/tmp.bPU5qiIpHi
• Continuous Benchmark (PR) / GPU Pytest benchmark (gh)
  Fatal Python error: Fatal Python error: Fatal Python error: Fatal Python error: Bus errorBus error
• Continuous Benchmark / GPU Pytest benchmark (gh)
  Fatal Python error: Fatal Python error: Fatal Python error: Fatal Python error: Bus errorBus error
• Habitat Tests on Linux / tests (3.9, 12.1) / linux-job (gh)
  RuntimeError: Command docker exec -t b1d4b6e47764f2b35f00c2d9ab160a960e768bd5daa3c03affcb247323669348 /exec failed with exit code 134

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
• Continuous Benchmark / CPU Pytest benchmark (gh) (trunk failure)
  ##[error]Process completed with exit code 135.
• Unit-tests on Linux / tests-olddeps (3.8, 11.6) / linux-job (gh) (trunk failure)
  test/test_modules.py::TestMultiAgent::test_multiagent_mlp_tdparams[True-batch0-6-True-True-3]
• Unit-tests on Windows / unittests-cpu / windows-job (gh) (trunk failure)
  test/test_collector.py::TestCompile::test_compiled_policy[device0-compile_policy2-MultiSyncDataCollector]

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

[vmoens]

aha good catch
LGTM