Workspace Integration: three sibling test failures (hypothesis missing, headless renderer, safe-retract)
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- Shell
- 星标
- 3
- 派生
- 1
- 平均合并
- 11 天 21 小时
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
personalrobotics/robot-code 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
-
ci nightly-fail
难度 4/5 1-2 天 新手友好度 18/100
personalrobotics/robot-code#168 ·
-
ci nightly-fail
难度 2/5 1-3 小时 新手友好度 35/100
personalrobotics/robot-code#167 ·
-
ci nightly-fail
难度 3/5 1-2 天 新手友好度 35/100
personalrobotics/robot-code#164 ·
-
ci nightly-fail
难度 3/5 1-2 天 新手友好度 35/100
personalrobotics/robot-code#163 ·
查看 personalrobotics/robot-code 的全部 Issue
相似的 Issue
-
bug needs-triage
难度 1/5 1 小时以内 新手友好度 78/100
mattpocock/skills#1281 ·
维护者通常 1 天内回复
-
github_actions
难度 2/5 1-3 小时 新手友好度 62/100
hiero-ledger/hiero-consensus-node#27621 ·
维护者通常 1 天内回复
-
application-issue
难度 2/5 1-3 小时 新手友好度 72/100
Installomator/Installomator#3427 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
software-mansion/argent#1483 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100