Reactivate camera tests that were accidentally deactivated.#950
Conversation
🤖 Isaac Lab-Arena Review BotSummaryThis PR restores the Findings🔵 Improvement: Test CoverageN/A — this is a CI-config change. It re-enables an existing test phase rather than adding new code, which is exactly the intent. VerdictShip it — the camera-test restoration is correct; the one marker note is optional. |
Greptile SummaryThis PR restores the accidentally dropped "Run in-process PhysX tests with cameras" step to the main
Confidence Score: 4/5Safe to merge — the change restores a previously working CI step and reorganizes job ordering without affecting logic. The newly added camera step in
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[pre_commit] --> B[test]
A --> C[tests_with_subprocess]
A --> D[test_gr00t_closedloop_e2e]
A --> E[test_curobo_deps]
A --> F[build_docs_pre_merge]
A --> UV_CHG[uv_changes]
UV_CHG --> UV_TEST[uv_test]
B --> B1[Newton tests]
B1 --> B2[PhysX without cameras]
B2 --> B3[PhysX with cameras RESTORED]
B3 --> B4[GR00T policy tests]
UV_TEST --> UV1[Newton tests]
UV1 --> UV2[PhysX without cameras]
UV2 --> UV3[PhysX with cameras - missing not with_newton]
UV3 --> UV4[Subprocess PhysX tests]
B --> IMG[build_and_push_image_post_merge]
E --> CUROBO[build_and_push_curobo_image_post_merge]
B --> CUROBO
Reviews (1): Last reviewed commit: "Reactivate camera tests that were accide..." | Re-trigger Greptile |
Summary
Reactivate camera tests that were accidentally deactivated.
Detailed description