TEST-INFRA: [flaky-tests] Unable to access CI run history #1727

Closed
opened 2026-04-02 23:36:35 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: fix/flaky-tests-ci-run-history-access
  • Commit Message: fix(ci): resolve CI run history access failure blocking flaky-test analysis
  • Milestone: v3.2.0
  • Parent Epic: #1678

Summary

The Test Infrastructure Improver agent is unable to access the CI run history for the cleveragents/cleveragents-core repository. This is preventing the agent from performing the flaky-tests analysis, which is essential for identifying and fixing intermittently failing tests.

Subtasks

  • Investigate why the Forgejo API is not returning any CI-related information for the repository
  • Ensure that the Test Infrastructure Improver agent has the necessary permissions to access the CI run history via the Forgejo API
  • Identify and document the correct API endpoints for accessing CI run history (e.g., /api/v1/repos/{owner}/{repo}/actions/runs)
  • Verify that CI workflow runs are being recorded and are accessible via the API
  • Update agent tooling/configuration to use the correct endpoints once identified
  • Confirm the flaky-tests analysis can be performed end-to-end after the fix

Definition of Done

  • The Test Infrastructure Improver agent is able to access the CI run history for the cleveragents/cleveragents-core repository
  • The agent is able to perform the flaky-tests analysis without API access errors
  • Root cause of the CI run history access failure is documented in this issue
  • All nox stages pass
  • Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

## Metadata - **Branch**: `fix/flaky-tests-ci-run-history-access` - **Commit Message**: `fix(ci): resolve CI run history access failure blocking flaky-test analysis` - **Milestone**: v3.2.0 - **Parent Epic**: #1678 ## Summary The Test Infrastructure Improver agent is unable to access the CI run history for the `cleveragents/cleveragents-core` repository. This is preventing the agent from performing the `flaky-tests` analysis, which is essential for identifying and fixing intermittently failing tests. ## Subtasks - [ ] Investigate why the Forgejo API is not returning any CI-related information for the repository - [ ] Ensure that the Test Infrastructure Improver agent has the necessary permissions to access the CI run history via the Forgejo API - [ ] Identify and document the correct API endpoints for accessing CI run history (e.g., `/api/v1/repos/{owner}/{repo}/actions/runs`) - [ ] Verify that CI workflow runs are being recorded and are accessible via the API - [ ] Update agent tooling/configuration to use the correct endpoints once identified - [ ] Confirm the `flaky-tests` analysis can be performed end-to-end after the fix ## Definition of Done - [ ] The Test Infrastructure Improver agent is able to access the CI run history for the `cleveragents/cleveragents-core` repository - [ ] The agent is able to perform the `flaky-tests` analysis without API access errors - [ ] Root cause of the CI run history access failure is documented in this issue - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.2.0 milestone 2026-04-02 23:37:20 +00:00
Author
Owner

Closing as duplicate of #1543 (TLS/clone failure — Priority/Critical, MoSCoW/Must Have).


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Closing as duplicate of #1543 (TLS/clone failure — Priority/Critical, MoSCoW/Must Have). --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo 2026-04-02 23:41:29 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#1727
No description provided.