TEST-INFRA: [ci-execution-time] Unable to clone repository cleveragents/cleveragents-core #1691

Closed
opened 2026-04-02 23:30:03 +00:00 by freemo · 2 comments
Owner

Metadata

  • Branch: fix/ci-execution-time-repo-clone-tls-sni
  • Commit Message: fix(ci): resolve TLS/SNI handshake failure blocking repository clone in CI
  • Milestone: v3.2.0
  • Parent Epic: #739

Background and Context

Worker agents running CI analysis tasks are unable to clone the cleveragents/cleveragents-core repository via HTTPS. This is a blocking infrastructure issue that prevents all automated test infrastructure analysis from proceeding.

The failure is caused by a Server Name Indication (SNI) issue on the Forgejo server at git.cleveragents.com, where the TLS handshake fails because the server name sent was not recognized.

Current Behavior

When attempting to clone via HTTPS, the following error is produced:

fatal: unable to access 'https://git.cleveragents.com/cleveragents/cleveragents-core.git/': gnutls_handshake() failed: The server name sent was not recognized

Troubleshooting Steps Taken:

  1. HTTPS Clone: Failed with the handshake error.
  2. HTTPS Clone with SSL Verification Disabled: Failed with the same error.
  3. HTTP Clone: Succeeded, but resulted in an empty repository.
  4. HTTPS Clone with Explicit Host Header: Failed with the same error.

Expected Behavior

Worker agents should be able to clone the repository via HTTPS without TLS/SNI errors, receiving a fully populated repository with all source files, CI configuration, and test infrastructure.

Acceptance Criteria

  • git clone https://git.cleveragents.com/cleveragents/cleveragents-core.git succeeds without TLS errors
  • The cloned repository contains all expected source files (non-empty)
  • CI pipeline jobs that depend on repository checkout complete successfully
  • All worker agents can access the repository for automated analysis tasks

Subtasks

  • Investigate and confirm the root cause of the SNI mismatch on git.cleveragents.com
  • Apply the appropriate server-side TLS/SNI fix (e.g., correct virtual host configuration, certificate SAN entries)
  • Verify HTTPS clone succeeds from multiple network environments
  • Confirm CI pipeline checkout steps pass end-to-end
  • Update CI workflow documentation if any workaround steps were added

Definition of Done

  • All subtasks above are completed
  • git clone https://git.cleveragents.com/cleveragents/cleveragents-core.git succeeds without error
  • The repository is non-empty after clone
  • CI pipeline passes all checkout-dependent jobs
  • Commit fix(ci): resolve TLS/SNI handshake failure blocking repository clone in CI pushed to branch fix/ci-execution-time-repo-clone-tls-sni
  • Associated PR is merged
  • All nox stages pass
  • Coverage >= 97%

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

## Metadata - **Branch**: `fix/ci-execution-time-repo-clone-tls-sni` - **Commit Message**: `fix(ci): resolve TLS/SNI handshake failure blocking repository clone in CI` - **Milestone**: v3.2.0 - **Parent Epic**: #739 ## Background and Context Worker agents running CI analysis tasks are unable to clone the `cleveragents/cleveragents-core` repository via HTTPS. This is a blocking infrastructure issue that prevents all automated test infrastructure analysis from proceeding. The failure is caused by a Server Name Indication (SNI) issue on the Forgejo server at `git.cleveragents.com`, where the TLS handshake fails because the server name sent was not recognized. ## Current Behavior When attempting to clone via HTTPS, the following error is produced: ``` fatal: unable to access 'https://git.cleveragents.com/cleveragents/cleveragents-core.git/': gnutls_handshake() failed: The server name sent was not recognized ``` **Troubleshooting Steps Taken:** 1. **HTTPS Clone:** Failed with the handshake error. 2. **HTTPS Clone with SSL Verification Disabled:** Failed with the same error. 3. **HTTP Clone:** Succeeded, but resulted in an empty repository. 4. **HTTPS Clone with Explicit Host Header:** Failed with the same error. ## Expected Behavior Worker agents should be able to clone the repository via HTTPS without TLS/SNI errors, receiving a fully populated repository with all source files, CI configuration, and test infrastructure. ## Acceptance Criteria - [ ] `git clone https://git.cleveragents.com/cleveragents/cleveragents-core.git` succeeds without TLS errors - [ ] The cloned repository contains all expected source files (non-empty) - [ ] CI pipeline jobs that depend on repository checkout complete successfully - [ ] All worker agents can access the repository for automated analysis tasks ## Subtasks - [ ] Investigate and confirm the root cause of the SNI mismatch on `git.cleveragents.com` - [ ] Apply the appropriate server-side TLS/SNI fix (e.g., correct virtual host configuration, certificate SAN entries) - [ ] Verify HTTPS clone succeeds from multiple network environments - [ ] Confirm CI pipeline checkout steps pass end-to-end - [ ] Update CI workflow documentation if any workaround steps were added ## Definition of Done - [ ] All subtasks above are completed - [ ] `git clone https://git.cleveragents.com/cleveragents/cleveragents-core.git` succeeds without error - [ ] The repository is non-empty after clone - [ ] CI pipeline passes all checkout-dependent jobs - [ ] Commit `fix(ci): resolve TLS/SNI handshake failure blocking repository clone in CI` pushed to branch `fix/ci-execution-time-repo-clone-tls-sni` - [ ] Associated PR is merged - [ ] 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:30:27 +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
Author
Owner

Closing as duplicate of #1532 (BUG-HUNT: TLS Configuration Error on git.cleveragents.com). This issue describes the same underlying TLS/repository clone failure that is already being tracked. Please follow #1532 and #1543 for updates on the fix.


Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

Closing as duplicate of #1532 (BUG-HUNT: TLS Configuration Error on git.cleveragents.com). This issue describes the same underlying TLS/repository clone failure that is already being tracked. Please follow #1532 and #1543 for updates on the fix. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
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#1691
No description provided.