Skip to content

codex TRACE conformance test fails on main; fix/codex-trace-pins was never pushed #73

Closed

Description

@imran-siddique

plugins/agentrust-codex/tests/test_codex_capture.py::test_signed_outputs_verify_and_pass_trace_level_zero fails on main, and has done throughout #65, #67, #69 and #72. Verified pre-existing each time by stashing the change under review and re-running on the same base, so it is not attributable to any of them.

TR-POL  PASS  policy.enforcement_mode is valid ('silent')
Result: FAIL  (8 checks, 1 failure(s), 0 skipped)

A local branch named fix/codex-trace-pins exists on at least one machine with the message "bump every trace pin to the v0.2 cutover", and it was never pushed. I referred to it in several PR bodies as "the branch addressing this", which was wrong: nothing upstream is fixing it. Correcting that here so the next person does not go looking.

Two things to decide: whether the pin bump is the actual fix, and whether this should be quarantined with xfail(strict=True) in the meantime so the suite is green and a regression is distinguishable from this known failure. Right now every codex run reports a failure, which trains people to ignore the count.

Activity

  1. imran-siddique commented on Aug 3, 2026

    @imran-siddique
    MemberAuthor

    Resolved on main, closing.

    test_signed_outputs_verify_and_pass_trace_level_zero lives in plugins/agentrust-codex/tests/test_codex_capture.py, which agentrust-codex-tests.yml runs via python -m pytest plugins/agentrust-codex/tests -q. That workflow has been green on main since 2026-08-01 17:47. The capture-core refactor carried the trace pin bump, so the v0.2 cutover this issue was waiting on has landed.

    Both open questions in the body are now moot: the pin bump was the fix, and no xfail quarantine is needed because the suite is genuinely green rather than green-by-suppression.

    For the record, the same v0.2 cutover defect existed in a second place. ramen-ai-cmcp hardcoded tag:agentrust.io,2026:trace-v0.1 and its conformance job had been failing on main since 2026-07-28, including the scheduled run at 09:38 today. That one is fixed in #85, which also unblocks #82, #83 and #84.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions