TEST-INFRA: [ci-execution-time] Unable to retrieve CI execution time data from Forgejo #7054

Open
opened 2026-04-10 07:27:29 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Branch: task/test-infra-ci-execution-time-data-unavailable
  • Commit Message: chore(ci): investigate and fix missing CI execution time reporting to Forgejo API
  • Milestone: (none — backlog, see note below)
  • Parent Epic: #5407

Summary

This issue documents the failure to retrieve CI execution time data from the Forgejo API. This prevents the test-infra-improver agent from analyzing CI performance and identifying optimization opportunities.

Duplicate Check

  • Search query: "CI execution time", "Forgejo API", "commit status"
  • Results: 0
  • Reasoning: This is a new issue documenting a specific technical roadblock.

Details

The test-infra-improver agent, when running in ci-execution-time mode, was unable to retrieve any CI-related timing information from the Forgejo API for the cleveragents/cleveragents-core repository.

The following methods were attempted:

  1. Commit Statuses API: Queried the /api/v1/repos/{owner}/{repo}/commits/{ref}/statuses endpoint for various commits, including pull request heads and the master branch head. All queries returned an empty result.
  2. Actions API: Queried the /api/v1/repos/{owner}/{repo}/actions/runs endpoint. This also returned an empty result, suggesting that the CI system is not integrated with Forgejo Actions.
  3. Pull Request Comments: Inspected the comments on several recent pull requests, but found no comments from any CI system that would contain timing information.

Impact

Without access to CI execution time data, it is impossible to programmatically identify slow test suites, flaky tests, or other performance bottlenecks in the CI pipeline. This severely limits our ability to automate test infrastructure improvements.

Proposed Solution

Investigate the CI/CD system used for the cleveragents/cleveragents-core repository and determine why it is not reporting build statuses back to Forgejo. The CI system should be configured to use the Forgejo Status API to report the status and duration of each check run. This will enable automated tools to access this data and perform performance analysis.

Subtasks

  • Identify the CI/CD system in use (e.g., Forgejo Actions, external CI) and confirm its integration method
  • Determine why commit statuses are not being reported to the Forgejo Statuses API
  • Configure the CI system to report check run statuses and durations via the Forgejo Status API
  • Verify that the test-infra-improver agent can successfully retrieve CI execution time data after the fix
  • Document the CI integration approach in the project's contributing guide or CI documentation

Definition of Done

  • The CI system is configured to report check run statuses and durations to the Forgejo API
  • The test-infra-improver agent is able to successfully retrieve CI execution time data
  • The agent is able to analyze the data and identify at least one performance bottleneck
  • All nox stages pass
  • Coverage >= 97%

Backlog note: This issue was discovered during autonomous operation
on milestone v3.8.0. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.


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

## Metadata - **Branch**: `task/test-infra-ci-execution-time-data-unavailable` - **Commit Message**: `chore(ci): investigate and fix missing CI execution time reporting to Forgejo API` - **Milestone**: *(none — backlog, see note below)* - **Parent Epic**: #5407 ## Summary This issue documents the failure to retrieve CI execution time data from the Forgejo API. This prevents the `test-infra-improver` agent from analyzing CI performance and identifying optimization opportunities. ### Duplicate Check - Search query: "CI execution time", "Forgejo API", "commit status" - Results: 0 - Reasoning: This is a new issue documenting a specific technical roadblock. ### Details The `test-infra-improver` agent, when running in `ci-execution-time` mode, was unable to retrieve any CI-related timing information from the Forgejo API for the `cleveragents/cleveragents-core` repository. The following methods were attempted: 1. **Commit Statuses API**: Queried the `/api/v1/repos/{owner}/{repo}/commits/{ref}/statuses` endpoint for various commits, including pull request heads and the `master` branch head. All queries returned an empty result. 2. **Actions API**: Queried the `/api/v1/repos/{owner}/{repo}/actions/runs` endpoint. This also returned an empty result, suggesting that the CI system is not integrated with Forgejo Actions. 3. **Pull Request Comments**: Inspected the comments on several recent pull requests, but found no comments from any CI system that would contain timing information. ### Impact Without access to CI execution time data, it is impossible to programmatically identify slow test suites, flaky tests, or other performance bottlenecks in the CI pipeline. This severely limits our ability to automate test infrastructure improvements. ### Proposed Solution Investigate the CI/CD system used for the `cleveragents/cleveragents-core` repository and determine why it is not reporting build statuses back to Forgejo. The CI system should be configured to use the Forgejo Status API to report the status and duration of each check run. This will enable automated tools to access this data and perform performance analysis. ## Subtasks - [ ] Identify the CI/CD system in use (e.g., Forgejo Actions, external CI) and confirm its integration method - [ ] Determine why commit statuses are not being reported to the Forgejo Statuses API - [ ] Configure the CI system to report check run statuses and durations via the Forgejo Status API - [ ] Verify that the `test-infra-improver` agent can successfully retrieve CI execution time data after the fix - [ ] Document the CI integration approach in the project's contributing guide or CI documentation ## Definition of Done - [ ] The CI system is configured to report check run statuses and durations to the Forgejo API - [ ] The `test-infra-improver` agent is able to successfully retrieve CI execution time data - [ ] The agent is able to analyze the data and identify at least one performance bottleneck - [ ] All nox stages pass - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.8.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: new-issue-creator
Author
Owner

Verified — CI infrastructure issue: unable to retrieve CI execution time data. MoSCoW: Could-have. Priority: Low.


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

✅ **Verified** — CI infrastructure issue: unable to retrieve CI execution time data. MoSCoW: Could-have. Priority: Low. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
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#7054
No description provided.