TEST-INFRA: [ci-pipeline-design] Unable to clone repository #1598

New issue

Closed

opened 2026-04-02 23:04:05 +00:00 by freemo · 2 comments

freemo commented

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

Owner

Metadata

Branch: fix/ci-clone-tls-sni-failure
Commit Message: fix(ci): resolve TLS/SNI handshake failure preventing repository clone
Milestone: v3.8.0
Parent Epic: (orphan — no TEST-INFRA Epic found; see orphan note below)

Description

The Test Infrastructure Improver agent is unable to clone the cleveragents/cleveragents-core repository, preventing all automated analysis.

Error:
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:

Attempted to clone with standard HTTPS authentication.
Attempted to clone with http.sslVerify=false to rule out certificate validation issues.

Both attempts failed with the same error, suggesting a potential Server Name Indication (SNI) or other server-side configuration issue.

This is a blocking issue for all automated test infrastructure analysis.

Related Issues: #1592, #1593 (similar TLS/clone failures reported previously)

Subtasks

Investigate the SNI/TLS configuration on git.cleveragents.com to identify the root cause
Verify that the server certificate includes the correct Subject Alternative Names (SANs)
Test clone via SSH as an alternative to HTTPS if TLS cannot be resolved quickly
Update CI pipeline configuration to use the correct host/protocol once resolved
Verify automated test infrastructure agent can successfully clone the repository
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, 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.
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
The Test Infrastructure Improver agent can successfully clone the repository without TLS errors.
All nox stages pass.
Coverage >= 97%.

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

## Metadata - **Branch**: `fix/ci-clone-tls-sni-failure` - **Commit Message**: `fix(ci): resolve TLS/SNI handshake failure preventing repository clone` - **Milestone**: v3.8.0 - **Parent Epic**: *(orphan — no TEST-INFRA Epic found; see orphan note below)* ## Description The Test Infrastructure Improver agent is unable to clone the `cleveragents/cleveragents-core` repository, preventing all automated analysis. **Error:** `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:** - Attempted to clone with standard HTTPS authentication. - Attempted to clone with `http.sslVerify=false` to rule out certificate validation issues. Both attempts failed with the same error, suggesting a potential Server Name Indication (SNI) or other server-side configuration issue. This is a blocking issue for all automated test infrastructure analysis. **Related Issues:** #1592, #1593 (similar TLS/clone failures reported previously) ## Subtasks - [ ] Investigate the SNI/TLS configuration on `git.cleveragents.com` to identify the root cause - [ ] Verify that the server certificate includes the correct Subject Alternative Names (SANs) - [ ] Test clone via SSH as an alternative to HTTPS if TLS cannot be resolved quickly - [ ] Update CI pipeline configuration to use the correct host/protocol once resolved - [ ] Verify automated test infrastructure agent can successfully clone the repository - [ ] 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, 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. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. - The Test Infrastructure Improver agent can successfully clone the repository without TLS errors. - All nox stages pass. - Coverage >= 97%. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo added this to the v3.7.0 milestone

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

freemo commented

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

Author

Owner

⚠️ Orphan Issue — Manual Linking Required

This issue was created without a parent Epic because no TEST-INFRA Epic was found in the repository. Per CONTRIBUTING.md, orphan issues are not permitted — every issue must belong to an Epic.

Action Required: A project maintainer must either:

Create a TEST-INFRA Epic (e.g., "Epic: Test Infrastructure Improvements") and link this issue as a child (this issue should block the parent Epic), or
Link this issue to an existing appropriate Epic.

Note: Similar issues #1592 and #1593 also appear to be orphaned with the same TLS/clone problem. This may indicate a recurring infrastructure issue that warrants a dedicated Epic.

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

⚠️ **Orphan Issue — Manual Linking Required** This issue was created without a parent Epic because no TEST-INFRA Epic was found in the repository. Per `CONTRIBUTING.md`, orphan issues are not permitted — every issue must belong to an Epic. **Action Required:** A project maintainer must either: 1. Create a `TEST-INFRA` Epic (e.g., "Epic: Test Infrastructure Improvements") and link this issue as a child (this issue should **block** the parent Epic), or 2. Link this issue to an existing appropriate Epic. **Note:** Similar issues #1592 and #1593 also appear to be orphaned with the same TLS/clone problem. This may indicate a recurring infrastructure issue that warrants a dedicated Epic. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo referenced this issue

2026-04-02 23:10:25 +00:00

TEST-INFRA: [ci-pipeline-design] Refactor CI pipeline to reduce redundant setup #1606

freemo commented

2026-04-02 23:16:15 +00:00

Author

Owner

Closing as duplicate of #1543.

This issue reports the same repository clone failure that is already tracked in #1543 (Priority/Critical, MoSCoW/Must Have, v3.7.0). All work should be consolidated there.

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

Closing as duplicate of #1543. This issue reports the same repository clone failure that is already tracked in #1543 (Priority/Critical, MoSCoW/Must Have, v3.7.0). All work should be consolidated there. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo

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