TEST-INFRA: [ci-execution-time] Unable to clone repository #1694

New issue

Closed

opened 2026-04-02 23:30:48 +00:00 by freemo · 1 comment

freemo commented

2026-04-02 23:30:48 +00:00

Owner

Metadata

Branch: fix/ci-execution-time-clone-failure
Commit Message: fix(ci): resolve repository clone failure due to TLS/SNI handshake error
Milestone: v3.8.0
Parent Epic: #1678

Background and Context

The Test Infrastructure Improver agent is unable to clone the cleveragents/cleveragents-core repository. This failure blocks all CI/CD pipeline analysis and improvement work scoped under the parent Epic (#1678 — CI Execution Time Optimization).

Current Behavior

The git clone command fails with the following error:

gnutls_handshake() failed: The server name sent was not recognized

This error occurs even when SSL verification is disabled (e.g., GIT_SSL_NO_VERIFY=true), indicating the issue is at the TLS/SNI layer of the server configuration rather than a certificate trust problem. As a result, no analysis of the codebase or CI/CD pipeline can be performed.

Expected Behavior

The git clone command should succeed, allowing agents and contributors to clone the repository without TLS/SNI errors. The server should correctly recognize the server name presented during the TLS handshake.

Acceptance Criteria

git clone https://git.cleverthis.com/cleveragents/cleveragents-core.git completes successfully from a standard CI runner environment
The TLS/SNI handshake error no longer occurs
SSL verification can be re-enabled (i.e., the fix does not rely on disabling SSL verification as a workaround)
All CI pipeline jobs that depend on repository cloning resume normal operation

Supporting Information

Error message: gnutls_handshake() failed: The server name sent was not recognized
The error persists even with GIT_SSL_NO_VERIFY=true, ruling out a certificate trust issue
Related duplicate/similar issues: #1673, #1666, #1663, #1660, #1659, #1655
Root cause is likely a misconfigured SNI (Server Name Indication) entry in the Forgejo/reverse-proxy server configuration

Subtasks

Investigate server-side TLS/SNI configuration on the Forgejo host (git.cleverthis.com)
Identify whether the SNI mismatch is caused by a reverse proxy (e.g., nginx/caddy) or the Forgejo service itself
Apply the appropriate server configuration fix to resolve the SNI recognition failure
Verify git clone succeeds from a clean CI runner environment with SSL verification enabled
Confirm all CI pipeline jobs that clone the repository resume normal operation
Run nox (all default sessions), fix any errors
Verify coverage >= 97% via nox -s coverage_report

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly (fix(ci): resolve repository clone failure due to TLS/SNI handshake error), followed by a blank line, then additional lines providing relevant details about the implementation.
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly (fix/ci-execution-time-clone-failure).
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
All nox stages pass.
Coverage >= 97%

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

## Metadata - **Branch**: `fix/ci-execution-time-clone-failure` - **Commit Message**: `fix(ci): resolve repository clone failure due to TLS/SNI handshake error` - **Milestone**: v3.8.0 - **Parent Epic**: #1678 ## Background and Context The Test Infrastructure Improver agent is unable to clone the `cleveragents/cleveragents-core` repository. This failure blocks all CI/CD pipeline analysis and improvement work scoped under the parent Epic (#1678 — CI Execution Time Optimization). ## Current Behavior The `git clone` command fails with the following error: ``` gnutls_handshake() failed: The server name sent was not recognized ``` This error occurs even when SSL verification is disabled (e.g., `GIT_SSL_NO_VERIFY=true`), indicating the issue is at the TLS/SNI layer of the server configuration rather than a certificate trust problem. As a result, no analysis of the codebase or CI/CD pipeline can be performed. ## Expected Behavior The `git clone` command should succeed, allowing agents and contributors to clone the repository without TLS/SNI errors. The server should correctly recognize the server name presented during the TLS handshake. ## Acceptance Criteria - [ ] `git clone https://git.cleverthis.com/cleveragents/cleveragents-core.git` completes successfully from a standard CI runner environment - [ ] The TLS/SNI handshake error no longer occurs - [ ] SSL verification can be re-enabled (i.e., the fix does not rely on disabling SSL verification as a workaround) - [ ] All CI pipeline jobs that depend on repository cloning resume normal operation ## Supporting Information - Error message: `gnutls_handshake() failed: The server name sent was not recognized` - The error persists even with `GIT_SSL_NO_VERIFY=true`, ruling out a certificate trust issue - Related duplicate/similar issues: #1673, #1666, #1663, #1660, #1659, #1655 - Root cause is likely a misconfigured SNI (Server Name Indication) entry in the Forgejo/reverse-proxy server configuration ## Subtasks - [ ] Investigate server-side TLS/SNI configuration on the Forgejo host (`git.cleverthis.com`) - [ ] Identify whether the SNI mismatch is caused by a reverse proxy (e.g., nginx/caddy) or the Forgejo service itself - [ ] Apply the appropriate server configuration fix to resolve the SNI recognition failure - [ ] Verify `git clone` succeeds from a clean CI runner environment with SSL verification enabled - [ ] Confirm all CI pipeline jobs that clone the repository resume normal operation - [ ] Run `nox` (all default sessions), fix any errors - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly (`fix(ci): resolve repository clone failure due to TLS/SNI handshake error`), followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly (`fix/ci-execution-time-clone-failure`). - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. - All nox stages pass. - Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo added this to the v3.8.0 milestone

2026-04-02 23:32:22 +00:00

freemo added a new dependency

2026-04-02 23:35:35 +00:00

#1678 Epic: CI Execution Time Optimization — Timeouts, Concurrency, and Coverage Artifact Sharing

freemo commented

2026-04-02 23:41:26 +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:26 +00:00