fix(tests): restore pytest 9-compatible docker_mock fixture registration #808
Labels
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/platform#808
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Spec sources (whitelist)
control-plane/platformctl/tests/conftest.pycontrol-plane/platformctl/tests/fixtures/docker_mock.pycontrol-plane/platformctl/tests/test_plan_integration.pydocs/forgejo-agent-operations.md§Issue RulesExtracted context
Do NOT read (unless escape hatch fires)
control-plane/platformctl/tools/— runtime implementation is out of scope; this is fixture registration only.modules/— module manifests do not affect this pytest fixture contract.Allowed touched paths
control-plane/platformctl/tests/conftest.py(modify)control-plane/platformctl/tests/test_plan_integration.py(read only unless a minimal assertion is needed)Why this exists (product-first)
Agents need the platformctl test suite to collect reliably on current pytest versions. The
docker_mockfixture is part of the read-only runtime planning test surface; losing fixture discovery turns a simple linter cleanup into a broken test harness.Why this matters now
The Antigravity audit found the pytest 9 compatibility issue, but the follow-up ruff cleanup appears to remove the import pytest needs for fixture registration. This should be made explicit and pinned with a focused test command before any branch cleanup is merged.
What "done" looks like
control-plane/platformctl/tests/conftest.pyregistersdocker_mockwithout using nestedpytest_plugins.PYTHONPATH=control-plane python3 -m pytest control-plane/platformctl/tests/test_plan_integration.pypasses.PYTHONPATH=control-plane python3 -m pytest control-plane/platformctl/testscollects without pytest-plugin deprecation errors.Scope
In scope:
docker_mock.Out of scope:
Suggested approach
pytest_pluginswith an explicit import that pytest can discover and ruff will not remove.test_plan_integration.pytest.Escape hatch
If pytest no longer needs this fixture import, comment with the exact pytest discovery evidence before deleting it. Do not silently accept an empty
conftest.pyjust because ruff reports an unused import.Unknowns / owner questions
Risk class
risk/runtime— test harness validates read-only runtime planning behavior.risk/process— bad lint cleanup can break agent-visible verification.Class of service
class/security-sensitiveTrace
antigravity/orders/audit-reconcile.Iskra judgment
pdurlej/platform#issue#808judge/p2,judge/codex-candidateiskraviaopenclawRationale: This is a small Codex-suitable CI fix with clear scoped files and low production blast radius, but it protects pytest compatibility for platformctl tests.
Caveat: The judgment relies on the supplied excerpt and does not verify the actual pytest failure locally.
Structured openclaw.judge.v0 payload