Workspace Integration: three sibling test failures (hypothesis missing, headless renderer, safe-retract)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by locating the Workspace Integration workflow that runs 38259945103, then inspect its sibling test and dependency setup. Check the named failures in test_admissibility.py, test_mujoco_collision_corpus.py, tests/test_feeding_session.py::test_detect_and_hide_food_in_sim, and test_safe_retract.py::test_stops_on_new_contact; the issue points to ada_mj/sensors.py:39 and linked issue #178. Done means the integration job handles the missing hypothesis extra and headless renderer, and the sibling failures are resolved or appropriately skipped.
Written by the indexing model from the issue text.
Description
Workspace Integration was disabled by GitHub for inactivity; I re-enabled it while landing #165. With mj_manipulator renamed to depend on sscbirrt (personalrobotics/mj_manipulator#176), every sibling now installs. Run 38259945103 (Python 3.11 and 3.12) fails on three things, none caused by #165:
- sscbirrt's tests import
hypothesis, itsdevextra, which the integration job doesn't install (test_admissibility.py,test_mujoco_collision_corpus.py). Fix: install the siblings' dev extras, or have the job skip a sibling's tests whose dev dependencies are missing. - ada_mj aborts in
tests/test_feeding_session.py::test_detect_and_hide_food_in_sim. The cause isada_mj/sensors.py:39, which builds amujoco.Rendereron the headless runner (Fatal Python error: Abortedinmujoco/rendering/classic/renderer.py). Fix: setMUJOCO_GL=egl(orosmesa) in the job, or skip rendering tests without a GL context. - mj_manipulator
test_safe_retract.py::test_stops_on_new_contactis personalrobotics/mj_manipulator#178: the new-contact stop fires at the first step. This is not IK.
Every other sibling passes: ada_assets 48, geodude 140, mj_manipulator 497 of 498, and the rest.
- Dominant language
- Shell
- Stars
- 3
- Forks
- 1
- Avg merge
- 11d 21h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from personalrobotics/robot-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
ci nightly-fail
Difficulty 4/5 1-2 days Newbie friendliness 18/100
personalrobotics/robot-code#168 ·
-
ci nightly-fail
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
personalrobotics/robot-code#167 ·
-
ci nightly-fail
Difficulty 3/5 1-2 days Newbie friendliness 35/100
personalrobotics/robot-code#164 ·
-
ci nightly-fail
Difficulty 3/5 1-2 days Newbie friendliness 35/100
personalrobotics/robot-code#163 ·
All issues in personalrobotics/robot-code
Similar issues
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
redhat-developer/rhdh-plugin-export-overlays#4391 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
graygarbage/HermesKey#20 ·
-
check-unsafe: source read errors become successful zero countsPossibly taken A pull request linked to this issue is open or already merged. Openreview-bot
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
midagedev/bloomery#151 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
mattpocock/skills#1269 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days