fix(test): evict sys.modules cache in _register_subcommands import error test #10928
Labels
Clear labels
auto/needs-reevaluation
controller-managed
overdue
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Needs Feedback
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
Currently being processed by an implementer worker.
Currently being processed by the merge driver.
Currently being processed by a reviewer worker.
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
Tracking issues used by the AI Automation system for agents to communicate and report.
Rebase conflict needs LLM conflict-resolver.
Failing CI needs implementer attention.
Documenting a driver incident or rollback.
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
aditya (Aditya Chhabra)
aleenaumair (Aleena Umair)
brent.edwards (Brent Edwards)
CoreRasurae (Luis Mendes)
drew (Drew Morris)
eugen.thaci (Eugen Thaci)
freemo (Jeffrey Phillips Freeman)
HAL9000 (HAL 9000)
HAL9001 (HAL9001)
hamza.khyari (Hamza Khyari)
hurui200320 (Rui Hu)
justin.morris
khird (Kyle Hird)
org.cleveragents
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cleveragents/cleveragents-core#10928
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "fix/cli-main-cov3-sysmodules-cache"
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?
Summary
cleveragents.cli.commandsand all its sub-packages/submodules fromsys.modulesbefore calling_register_subcommands(), so the__import__patch actually takes effect (the module is normally cached from the eager import-time call incli/main.py).except Exceptiontoexcept BaseExceptionin the step so thatSystemExit(1)raised by_register_subcommands()is properly caught and stored (SystemExit extends BaseException, not Exception).Closes #10816
Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor
PR Fix Attempt — Tier 0: qwen — Success
Reviewed PR #10928 and ran all quality gates. The code changes are correct and all gates pass:
No reviewer feedback (REQUEST_CHANGES) to address. No CI failures to diagnose.
PR Summary: Evicts
cleveragents.cli.commandsfromsys.modulesbefore calling_register_subcommands()so the__import__patch takes effect. Changedexcept Exceptiontoexcept BaseExceptionto catchSystemExit. Restores originalsys.modulesentries via cleanup callback.Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor
Review Summary
This PR fixes a broken Behave test scenario identified in issue #10816. The
_register_subcommands handles import failure gracefullytest was failing becausecleveragents.cli.commandswas already cached insys.moduleswhen the test ran, causing the__import__patch to have no effect.Changes Reviewed (1 file:
features/steps/cli_main_cov3_steps.py)Three improvements were made:
sys.modules eviction (correct) — Saves a snapshot of
cleveragents.cli.commandsand all sub-packages fromsys.modules, deletes them, then restores viacontext.add_cleanup(). This ensures the patched__import__is actually invoked.except BaseException(correct) — Changed fromexcept Exceptiontoexcept BaseExceptionso thatSystemExit(1)raised by_register_subcommands()on import failure is properly caught.SystemExitinherits fromBaseException, notException, so the old code would never catch it.Cleanup pattern consistency (correct) — Moved
patcher_builtins.stop()from afinallyblock tocontext.add_cleanup(patcher_builtins.stop), making it consistent with the existing cleanup pattern forpatcher_console. Also removed the now-unnecessaryfinallyblock.CI Status
features/steps/.Category-by-Category Assessment
# type: ignoreaddedNon-blocking Suggestions
Type/label. Per the contributing guide, exactly oneType/label should be applied (likelyType/Testinggiven this is a test fix).v3.2.0(m3); the PR should have the same milestone assigned.Overall: clean, correct, and necessary test fix.
Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker
Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker
PR Fix Attempt — Tier 0: qwen — Success
What was done
fix/cli-main-cov3-sysmodules-cache) into an isolated workspace.nox -s lint,nox -s format -- --check, andnox -s typecheckall passed.ruff format --checkrevealed thatfeatures/steps/cli_main_cov3_steps.pyneeded reformatting (thepatch.object(mod, "get_err_console", return_value=mock_err_console)call was being split across lines in a way ruff did not approve — it wanted it in a multi-linepatch.object(call).nox -s format— reformatted 1 file.d3b3ae70):style: reformat cli_main_cov3_steps.py for rufforigin/fix/cli-main-cov3-sysmodules-cache.Review feedback
No
REQUEST_CHANGESreviews exist. The automated review (agent: pr-review-worker, state: COMMENT) confirmed the code changes are correct:except BaseExceptioncorrectly catchesSystemExitQuality gate results
Changed files
features/steps/cli_main_cov3_steps.py— 3 insertions, 1 deletion (formatting only)Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor
PR Review Summary
What was reviewed
This PR fixes the
cli_main_cov3Behave scenario@tdd_issue_10816 _register_subcommands handles import failure gracefullywhich was broken becausecleveragents.cli.commandswas already cached insys.modules, preventing the__import__patch from taking effect. The only file changed isfeatures/steps/cli_main_cov3_steps.py(27 additions, 5 deletions across two commits).Review verdict: APPROVED
All 10 review categories pass:
Correctness ✅ — The fix properly addresses the root cause:
cleveragents.cli.commandsand all its sub-packages are evicted fromsys.modulesbefore calling_register_subcommands(), so the__import__patch actually takes effect. Additionally,except Exceptionis changed toexcept BaseExceptionto properly catchSystemExit(1)raised during import failure (SystemExitextendsBaseException, notException).Specification Alignment ✅ — No production code changes. The fix is entirely in test infrastructure and is consistent with the test's purpose.
Test Quality ✅ — The step definition now correctly catches
SystemExit(1)by usingexcept BaseException. Cleanup withcontext.add_cleanup()ensures originalsys.modulesentries are restored for other test scenarios, preventing cross-test pollution. Good error path coverage.Type Safety ✅ — No
# type: ignorecomments. Function signature already typed. All new variables are properly inferred.Readability ✅ — The docstring clearly explains the why (sys.modules caching). The
module_namevariable eliminates the magic string.context.add_cleanup()is idiomatic Behave pattern. Code is easy to follow.Performance ✅ — No performance concerns in a test context. The
for key in list(sys.modules)pattern correctly iterates a copy without mutating the dict during iteration.Security ✅ — No security concerns. Test-only code, no secrets, no external input.
Code Style ✅ — ruff-compliant (verified via second commit that applied
nox -s format). Clean code following SOLID principles. Minor note:import sysis inside the function rather than at module top — functionally correct but PEP 8 prefers top-of-file imports.Documentation ✅ — Comprehensive docstring and inline comments explaining the rationale for each change (why
BaseException, why sys.modules eviction, why cleanup callback).Commit and PR Quality ✅ — Two atomic commits in Conventional Changelog format. PR body includes
Closes #10816. Second commit properly addresses the ruff formatting feedback.Non-blocking suggestions:
Type/label (CONTRIBUTING.md requires exactly one Type/ label;Type/Testingis appropriate here).v3.2.0).CI status: All quality gates passed. CI checks show pending in the API, but the automated quality gate runs confirm lint, typecheck, unit_tests, integration_tests, and e2e_tests all passed successfully.
Overall assessment: Clean, focused fix that solves the root cause with proper cleanup. Approving.
Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker
Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker
Re-Review of PR #10928 — fix(test): evict sys.modules cache in _register_subcommands import error test
Prior feedback status
Type/label and milestone. These items remain as non-blocking observations (detailed below).REQUEST_CHANGESreviews existed, so no prior blocking feedback items needed verification.Changes since last review
Commit
d3b3ae70—style: reformat cli_main_cov3_steps.py for ruffpatch.object(mod, "get_err_console", return_value=mock_err_console)into the multi-line form ruff prefers. Verified correct via diff.Full 10-Category Review
1. Correctness ✅ — PR correctly addresses the root cause in issue #10816.
cleveragents.cli.commandsand all sub-packages are evicted fromsys.modulesbefore_register_subcommands()is called, so the__import__patch actually fires. Afterward, original entries are restored viacontext.add_cleanup().2. Specification Alignment ✅ — No production code changes. Entirely within test step definitions.
3. Test Quality ✅ — Three correct improvements:
except BaseExceptioncorrectly catchesSystemExit(1)(extendsBaseException, notException)context.add_cleanup()patterns prevent cross-test pollution4. Type Safety ✅ — No
# type: ignore. All variables properly typed/annotated.import sysinside the function is functionally acceptable for a Behave step.5. Readability ✅ — Variable
module_nameeliminates the magic string. New docstring clearly explains sys.modules rationale. Well-placed inline comments.6. Performance ✅ — No concerns in test context.
list(sys.modules)correctly iterates a copy during dict mutation.7. Security ✅ — Test code only, no external input, no secrets, no unsafe patterns.
8. Code Style ✅ — ruff-compliant. Second commit resolved formatting. Consistent with surrounding code in
cli_main_cov3_steps.py.9. Documentation ✅ — Docstring updated with three-sentence explanation. Three inline comments explain rationale for sys.modules eviction,
BaseException, and cleanup callbacks.10. Commit and PR Quality ⚠️ — Two non-blocking metadata items:
Type/label — Contributing guide requires exactly oneType/label per PR.Type/Testingis appropriate here.v3.2.0(m3); the PR should carry the same milestone.CI Status — All Green
14/14 checks passing: lint, typecheck, security, unit_tests, integration_tests, e2e_tests, coverage, build, docker, helm, push-validation, quality, benchmark-publish, status-check.
Verdict: COMMENT (non-blocking observations only)
All substantive code changes are correct, well-tested, and CI is fully green. The two metadata issues (missing label, missing milestone) are non-blocking and should be addressed separately. No blocking code issues found.
Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker
Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker
d3b3ae7086to756ecb1ca8756ecb1ca8toc1820e6026c1820e6026tob747f1aab1Implementation Attempt — Tier 0: qwen — Success
PR #10928 is already merged (merged_at: 2026-04-30T19:56:55Z). No code changes are pending.
Analysis
The PR ("fix(test): evict sys.modules cache in _register_subcommands import error test") was merged into master by HAL9000. It fixes issue #10816 (a Behave test scenario that failed due to
cleveragents.cli.commandsbeing cached insys.modules).Review Status
CI Status at Merge
All quality gates passed: lint ✓, typecheck ✓, unit_tests ✓, integration_tests ✓, e2e_tests ✓, coverage ✓, security ✓, build ✓, docker ✓, helm ✓
Note on Work Title
The work_title provided ("[CI] Optimize benchmark-regression test execution time via caching and parallelism") does not match the actual PR title. The PR was a Behave test infrastructure fix, not a benchmark optimization. This appears to be a metadata assignment mismatch.
No further action required — this PR is fully resolved.
Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor