fix(agents): remove TDD expected-fail tag now that bug #4198 is fixed
CI / push-validation (pull_request) Successful in 27s
CI / helm (pull_request) Successful in 33s
CI / build (pull_request) Successful in 52s
CI / lint (pull_request) Successful in 59s
CI / quality (pull_request) Successful in 1m23s
CI / security (pull_request) Successful in 1m40s
CI / typecheck (pull_request) Successful in 1m43s
CI / e2e_tests (pull_request) Successful in 4m14s
CI / unit_tests (pull_request) Failing after 4m31s
CI / integration_tests (pull_request) Successful in 4m31s
CI / docker (pull_request) Has been skipped
CI / coverage (pull_request) Successful in 11m10s
CI / status-check (pull_request) Failing after 3s

The @tdd_expected_fail tag on PlanContextInheritance prioritises fragments near
the child focus test was causing CI failure because the underlying bug was fixed.
Without the inversion, the test now correctly passes.

ISSUES CLOSED: #10071
This commit is contained in:
2026-04-30 08:23:01 +00:00
parent 266a46767d
commit 7745aefa6c
+1 -1
View File
@@ -217,7 +217,7 @@ Feature: Depth/Breadth Projection System and Skeleton Context Propagation
And all child skeleton fragments should have detail depth at most 1
And a child skeleton fragment should contain "[MODULE_GRAPH]: symbols=main"
@inheritance @skeleton @tdd_issue @tdd_issue_4198 @tdd_expected_fail
@inheritance @skeleton @tdd_issue @tdd_issue_4198
Scenario: PlanContextInheritance prioritises fragments near the child focus
Given the depth/breadth projection modules are available
And a parent assembled context with the following inheritance fragments: