TEST-INFRA: [ci-execution-time] Unable to access CI execution times #3322

New issue

Open

opened 2026-04-05 09:49:26 +00:00 by freemo · 1 comment

freemo commented

2026-04-05 09:49:26 +00:00

Owner

Metadata

Branch: fix/test-infra-ci-execution-time-tool-access
Commit Message: fix(test-infra): expose CI execution time data to analysis tooling
Milestone: (none — see backlog note below)
Parent Epic: #3204

Subtasks

Investigate which CI data sources (Forgejo API, CI runner logs, artifact storage) expose per-job execution times
Determine whether the Forgejo API /repos/{owner}/{repo}/actions/runs endpoint or equivalent provides timing data
Expose or document the correct tool/API path for retrieving CI execution times per pull request
Re-run the ci-execution-time analysis (issue #3205) once access is confirmed

Definition of Done

CI execution time data is accessible via an available tool or documented API call
The ci-execution-time analysis (#3205) can be completed end-to-end without tool failures
Any workaround or new tooling is documented in the test infrastructure runbook
All nox stages pass
Coverage >= 97%

I am unable to complete the 'ci-execution-time' analysis because I cannot access the CI execution times for pull requests. The available tools do not provide this information, and my attempts to work around this have been unsuccessful due to issues with large file handling and tool restrictions.

Specifically, I have tried:

Listing all pull requests, which resulted in a truncated file that I couldn't parse.
Listing pull requests with pagination, which also resulted in a truncated file.
Reading the truncated files with read, grep, and bash with cat, head, and grep, all of which failed or gave me truncated results.
Listing commits and extracting pull request numbers from the commit messages.
Getting the details of individual pull requests, which did not contain the CI execution time.

Without access to CI execution times, I cannot identify slow tests and propose improvements.

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: ca-new-issue-creator

## Metadata - **Branch**: `fix/test-infra-ci-execution-time-tool-access` - **Commit Message**: `fix(test-infra): expose CI execution time data to analysis tooling` - **Milestone**: *(none — see backlog note below)* - **Parent Epic**: #3204 ## Subtasks - [ ] Investigate which CI data sources (Forgejo API, CI runner logs, artifact storage) expose per-job execution times - [ ] Determine whether the Forgejo API `/repos/{owner}/{repo}/actions/runs` endpoint or equivalent provides timing data - [ ] Expose or document the correct tool/API path for retrieving CI execution times per pull request - [ ] Re-run the `ci-execution-time` analysis (issue #3205) once access is confirmed ## Definition of Done - [ ] CI execution time data is accessible via an available tool or documented API call - [ ] The `ci-execution-time` analysis (#3205) can be completed end-to-end without tool failures - [ ] Any workaround or new tooling is documented in the test infrastructure runbook - [ ] All nox stages pass - [ ] Coverage >= 97% --- I am unable to complete the 'ci-execution-time' analysis because I cannot access the CI execution times for pull requests. The available tools do not provide this information, and my attempts to work around this have been unsuccessful due to issues with large file handling and tool restrictions. Specifically, I have tried: - Listing all pull requests, which resulted in a truncated file that I couldn't parse. - Listing pull requests with pagination, which also resulted in a truncated file. - Reading the truncated files with `read`, `grep`, and `bash` with `cat`, `head`, and `grep`, all of which failed or gave me truncated results. - Listing commits and extracting pull request numbers from the commit messages. - Getting the details of individual pull requests, which did not contain the CI execution time. Without access to CI execution times, I cannot identify slow tests and propose improvements. > **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: ca-new-issue-creator

freemo added a new dependency

2026-04-05 09:54:45 +00:00

#3205 TEST-INFRA: [ci-execution-time] Analyze CI execution time

freemo added a new dependency

2026-04-05 09:57:16 +00:00

#3204 TEST-INFRA: Parent issue for test infrastructure improvements

freemo added the

MoSCoW

Could have

label

2026-04-05 10:03:57 +00:00

freemo commented

2026-04-05 10:07:03 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Backlog (confirmed — CI execution time analysis is a tooling concern)
Milestone: v3.8.0 (CI improvements belong in M9)
MoSCoW: Could Have — CI optimization is desirable but not blocking any milestone.

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog (confirmed — CI execution time analysis is a tooling concern) - **Milestone**: v3.8.0 (CI improvements belong in M9) - **MoSCoW**: Could Have — CI optimization is desirable but not blocking any milestone. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo added this to the v3.8.0 milestone

2026-04-05 10:16:14 +00:00

freemo removed this from the v3.8.0 milestone

2026-04-06 23:59:51 +00:00