cleveragents/cleveragents-core

Fork 3

TEST-INFRA: [flaky-tests] Unable to clone repository #1673

New issue

Closed

opened 2026-04-02 23:27:29 +00:00 by freemo · 3 comments

freemo commented

2026-04-02 23:27:29 +00:00

Owner

Metadata

Branch: fix/test-infra-clone-tls-handshake
Commit Message: fix(ci): resolve TLS handshake failure preventing repository clone
Milestone: v3.2.0
Parent Epic: (see orphan note below)

Background and Context

As a Test Infrastructure Improver, the ability to clone the cleveragents/cleveragents-core repository is a prerequisite for all test suite analysis and CI pipeline work. A TLS handshake failure is blocking this entirely.

User Story:
As a Test Infrastructure Improver, I need to be able to clone the cleveragents/cleveragents-core repository so that I can analyze the test suite for flaky tests.

Current Behavior / Reproduction Steps

Run the command git clone https://<FORGEJO_PAT>@git.cleveragents.com/cleveragents/cleveragents-core.git
The command fails with the error gnutls_handshake() failed: The server name sent was not recognized
Run the command git -c http.sslVerify=false clone https://<FORGEJO_PAT>@git.cleveragents.com/cleveragents/cleveragents-core.git
The command fails with the same error.

Actual Behavior:
The git clone command fails with a TLS handshake error, even when SSL verification is disabled. This prevents any analysis of the repository.

Expected Behavior

The repository should be cloned successfully without TLS/SNI errors.

Impact

This is a critical issue that blocks all test infrastructure improvement work.

Subtasks

Investigate the TLS/SNI configuration for git.cleveragents.com
Determine whether the issue is a missing SNI entry, misconfigured certificate, or DNS/proxy misconfiguration
Apply the appropriate fix (e.g., update server TLS config, add SNI hostname, or update client clone URL)
Verify git clone succeeds from the CI environment
Verify git clone succeeds with SSL verification enabled
Update CI pipeline configuration if the clone URL or method needs to change

Definition of Done

All subtasks above are completed and checked off
git clone https://<FORGEJO_PAT>@git.cleveragents.com/cleveragents/cleveragents-core.git succeeds without TLS errors
SSL verification is not disabled as a workaround (fix is proper, not a bypass)
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly
The commit is submitted as a pull request to master, reviewed, and merged
All nox stages pass
Coverage >= 97%

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

## Metadata - **Branch**: `fix/test-infra-clone-tls-handshake` - **Commit Message**: `fix(ci): resolve TLS handshake failure preventing repository clone` - **Milestone**: v3.2.0 - **Parent Epic**: *(see orphan note below)* ## Background and Context As a Test Infrastructure Improver, the ability to clone the `cleveragents/cleveragents-core` repository is a prerequisite for all test suite analysis and CI pipeline work. A TLS handshake failure is blocking this entirely. **User Story:** As a Test Infrastructure Improver, I need to be able to clone the `cleveragents/cleveragents-core` repository so that I can analyze the test suite for flaky tests. ## Current Behavior / Reproduction Steps 1. Run the command `git clone https://<FORGEJO_PAT>@git.cleveragents.com/cleveragents/cleveragents-core.git` 2. The command fails with the error `gnutls_handshake() failed: The server name sent was not recognized` 3. Run the command `git -c http.sslVerify=false clone https://<FORGEJO_PAT>@git.cleveragents.com/cleveragents/cleveragents-core.git` 4. The command fails with the same error. **Actual Behavior:** The `git clone` command fails with a TLS handshake error, even when SSL verification is disabled. This prevents any analysis of the repository. ## Expected Behavior The repository should be cloned successfully without TLS/SNI errors. ## Impact This is a critical issue that blocks all test infrastructure improvement work. ## Subtasks - [ ] Investigate the TLS/SNI configuration for `git.cleveragents.com` - [ ] Determine whether the issue is a missing SNI entry, misconfigured certificate, or DNS/proxy misconfiguration - [ ] Apply the appropriate fix (e.g., update server TLS config, add SNI hostname, or update client clone URL) - [ ] Verify `git clone` succeeds from the CI environment - [ ] Verify `git clone` succeeds with SSL verification enabled - [ ] Update CI pipeline configuration if the clone URL or method needs to change ## Definition of Done - [ ] All subtasks above are completed and checked off - [ ] `git clone https://<FORGEJO_PAT>@git.cleveragents.com/cleveragents/cleveragents-core.git` succeeds without TLS errors - [ ] SSL verification is not disabled as a workaround (fix is proper, not a bypass) - [ ] A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly - [ ] The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly - [ ] The commit is submitted as a **pull request** to `master`, reviewed, and **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:29:41 +00:00

freemo commented

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

Author

Owner

⚠️ Orphan Issue — Manual Linking Required

A thorough search of all open and closed issues in this repository found no existing TEST-INFRA parent Epic to link this issue to. Per CONTRIBUTING.md, orphan issues are not permitted — every issue must be linked to a parent Epic via Forgejo's dependency system (child blocks parent).

Action Required: A project maintainer must either:

Identify an existing Epic that this issue belongs to and create the dependency link manually, or
Create a new Type/Epic issue for Test Infrastructure Improvement work, then link this issue as a child (this issue blocks the new Epic).

Once the parent Epic is identified, the dependency can be created via:

curl -s -X POST "https://git.cleverthis.com/api/v1/repos/cleveragents/cleveragents-core/issues/1673/blocks" \
  -H "Authorization: token <FORGEJO_PAT>" \
  -H "Content-Type: application/json" \
  -d '{"dependency_id": <PARENT_EPIC_NUMBER>}'

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

⚠️ **Orphan Issue — Manual Linking Required** A thorough search of all open and closed issues in this repository found **no existing TEST-INFRA parent Epic** to link this issue to. Per `CONTRIBUTING.md`, orphan issues are not permitted — every issue must be linked to a parent Epic via Forgejo's dependency system (child **blocks** parent). **Action Required:** A project maintainer must either: 1. Identify an existing Epic that this issue belongs to and create the dependency link manually, **or** 2. Create a new `Type/Epic` issue for Test Infrastructure Improvement work, then link this issue as a child (this issue **blocks** the new Epic). Once the parent Epic is identified, the dependency can be created via: ```bash curl -s -X POST "https://git.cleverthis.com/api/v1/repos/cleveragents/cleveragents-core/issues/1673/blocks" \ -H "Authorization: token <FORGEJO_PAT>" \ -H "Content-Type: application/json" \ -d '{"dependency_id": <PARENT_EPIC_NUMBER>}' ``` --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo referenced this issue

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

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

freemo commented

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

Author

Owner

Closing as duplicate of #1543. Issue #1543 is the canonical tracking issue for the TLS/git-clone failure. Multiple issues have been filed about the same underlying TLS configuration problem.

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

Closing as duplicate of #1543. Issue #1543 is the canonical tracking issue for the TLS/git-clone failure. Multiple issues have been filed about the same underlying TLS configuration problem. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

freemo closed this issue

2026-04-02 23:34:21 +00:00

freemo referenced this issue

2026-04-02 23:40:27 +00:00

[Automated] Backlog Groomer Session State — v3.7.0 #1463

freemo commented

2026-04-02 23:42:08 +00:00

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

freemo referenced this issue

2026-04-02 23:52:50 +00:00

Proposal: improve ca-test-infra-improver — prevent massive duplicate issue creation #1802

freemo referenced this issue

2026-04-02 23:53:43 +00:00

Proposal: improve ca-test-infra-improver — graceful handling of clone and tool failures #1809

freemo referenced this issue

2026-04-02 23:55:03 +00:00

[Automated] Backlog Groomer Session State — v3.7.0 #1463

freemo referenced this issue

2026-04-05 06:50:14 +00:00