Skip to content

πŸ›πŸ§‘β€πŸ’» - Bugbot partition exhausts unusable output retries without a diagnostic reasonΒ #920

Closed

Description

@efraespada

Is there an existing issue for this?

  • I have searched the existing issues.

Which actions are affected?

Pull Request

Which platforms are affected?

Linux

Description

The native Bugbot run for Domus #29 at fbb4cfd1d8160e63a6b4d62e4ac118fb2f946a0c failed after admitting its agent and exhausting the three query attempts for partition 1. It published a failed review check with agent.failed and retained the previous findings. The diagnostic only says the admitted agent did not produce a usable result, so the consumer cannot distinguish the invalid-output cause from execution infrastructure using the published result.

Reproducing the issue

Inspect run 42339188172, first attempt, and review check 128303665175. Context selection completed with 175 files and 26 bounded diff partitions. Maximum analysis concurrency was 2. Partition 1 retried at 04:37:23 and 04:38:08 UTC after unusable output. The failure was published at 04:40:15 UTC with four completed partitions and no published or resolved findings.

copilot Version

vypdev/copilot@v3. The admitted agent reports codex-cli 0.167.0, provider codex, model gpt-6-luna.

Relevant Log Output

Correlation 2ef76976-eaab-42e1-8c00-126602416b25. Telemetry has failedAnalysisPartitionOrdinal=1, failedAnalysisPartitionCategory=agent.failed, completedAnalysisPartitions=4, analysisPartitions=26, elapsedMs=198374, outcome=failed and errorCategory=applicationerror. No usable agent result or specific sanitized validation reason accompanies the published failure.

Additional context and comments

One unchanged-head workflow retry is running because the check marks the failure retryable. The original scope and review gates remain preserved. The review previously completed on the identical production runtime at 3d89052. The two follow-up commits add real restored-exclusion regression evidence and correct roadmap text, followed by the test formatter adjustment. This report concerns the failed review execution and its diagnostic boundary.

Activity

  1. added
    bugSomething isn't working
    bugfixSomething isn't working
    on Nov 7, 2026
  2. added theissue type on Nov 7, 2026
  3. moved this to Todo in vypdevon Nov 7, 2026
  4. vypbot commented on Nov 7, 2026

    @vypbot
    Contributor

    Hi! I’m @vypbot, the Copilot assistant for this repository.

    I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.

    Try /copilot help to see the available commands, or mention @vypbot with your question.

  5. efraespada commented on Nov 7, 2026

    @efraespada
    MemberAuthor

    The single unchanged-head retry completed successfully. Review check 128306495261 on fbb4cfd1d8160e63a6b4d62e4ac118fb2f946a0c is green with lifecycle ready, fixed=16, obsolete=4 and dismissed=7. Bugbot reports completed after 676,444 ms with no remaining findings. The failure and diagnostic boundary above remain reproducible in attempt 1. Product runtime bytes stayed identical throughout the retry.

  6. moved this from Todo to In Progress in vypdevon Nov 8, 2026
  7. added
    branchedIndicates that a branch has been created for this issue.
    on Nov 8, 2026
  8. changed the title [-]πŸ› - Bugbot partition exhausts unusable output retries without a diagnostic reason[/-] [+]πŸ›πŸ§‘β€πŸ’» - Bugbot partition exhausts unusable output retries without a diagnostic reason[/+] on Nov 8, 2026
  9. added
    state:workingWork can proceed on the verified branch or without a branch.
    on Nov 8, 2026
  10. 7 remaining items

  11. vypbot commented on Nov 8, 2026

    @vypbot
    Contributor

    Issue closed β€” historical progress

    Current status: closed as completed.

    The last estimate is retained below as history. Closure does not certify a new percentage, tests, or branch alignment.

    Action required: none for this closed issue. If work continues, reopen the issue; a fresh assessment can update this same card.

    Last assessment before closure (historical)

    scope:5102e2710edd27447baed325aeac2fc9580eb28cb9ee68031ba1e2a60206a972

    Progress: 100% β€” complete

    > Current status: [R15] The native Bugbot run for Domus #29 at fbb4cfd1d8160e63a6b4d62e4ac118fb2f946a0c failed after admitting its agent and exhausting the three query attempts for partition 1. It published a failed review check with agent.failed and retained the previous findings. The diagnostic only says the admitted agent did not produce a usable result, so the consumer cannot distinguish the invalid-output cause from execution infrastructure using the published result. β€” Completed Bugbot response exhaustion now carries a closed reason, while provider and process failures retain separate classifications.

    No action required.

  12. vypbot commented on Nov 8, 2026

    @vypbot
    Contributor

    Issue closed: synchronization recommendation retired

    No branch synchronization is required for this closed issue.

    The previous recommendation is historical. Issue closure does not certify that the branches are synchronized.

  13. moved this from In Progress to Done in vypdevon Nov 8, 2026
  14. removed
    state:workingWork can proceed on the verified branch or without a branch.
    on Nov 8, 2026
  15. efraespada commented on Nov 19, 2026

    @efraespada
    MemberAuthor

    Released consumer occurrence on Domus #142

    Domus #142 at 9f2d2588e1ba829a7b4d1b9b1917cc5ed703e56b encountered the opaque partition-exhaustion failure with vypdev/copilot@v3.10.13 and admitted codex-cli 0.170.0, provider codex, model gpt-6-luna. The ready-for-review run completed with failed Copilot / Review after 664,807 ms. Run 44470305682, review check

    The log reports four analysis partitions with maximum concurrency two. Partitions 2, 3 and 4 completed. Partition 1 repeatedly reached generated-source candidate verification, then its admitted child operation exited with status 1 and category unclassified. Three bounded partition attempts were exhausted. The final telemetry reports failedAnalysisPartitionOrdinal=1, failedAnalysisPartitionCategory=agent.failed, completedAnalysisPartitions=3, candidateFindings=0, publishedFindings=0 and errorCategory=applicationerror.

    The published diagnostic states that the admitted agent did not produce a usable result and gives reference 676b829d-e704-43f2-819c-82ec9572394f. It supplies no specific sanitized terminal cause. The native run has no diagnostic artifacts. A fresh GraphQL read finds zero review threads and zero submitted reviews. Review coverage remains incomplete.

    One unchanged-head retry has been requested with gh run rerun --failed. Current-head Branch Sync, Commit and Verification have succeeded. The application CI continues on self-hosted runners, including both CPU families. The consumer maintainer has authorized proceeding past a recorded Copilot execution blocker once all product checks pass and contributor review has resolved any valid findings. The current PR records this bounded exception and its remaining gates.

    Please reconcile this occurrence with #920's released diagnostic coverage and the candidate-verification boundary tracked by #950. The exact underlying process failure is unclassified in the available consumer evidence.

    Unchanged-head retry outcome

    Attempt 2 completed all four partitions in 510,261 ms and published no new findings. Its Review check is neutral because it retains an existing valid finding, Saving an unchanged assignment is misreported as a conflict. The consumer has reproduced that behavior in seven English/Spanish component regressions and is preparing Edge.49. The earlier opaque child-process diagnostic remains available in attempt 1. Attempt 2, retained finding

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

Metadata

Metadata

Assignees

Labels

100%Progress: 100%branchedIndicates that a branch has been created for this issue.bugSomething isn't workingbugfixSomething isn't workingsize: XXLIndicates an extremely large task or issue that requires significant time and effort to complete.

Type

Projects

  • Status
    Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions