bstein/bstein-dev-home
1
0
Fork 0
Code Issues 800 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[hermes] bstein-dev-home #545: transient_infra_failure #81

New Issue
Open
opened 2026-09-23 04:07:38 +00:00 by hermes-automation · 0 comments
hermes-automation commented 2026-09-23 04:07:38 +00:00
Copy Link

Hermes auto-triage classified incident bstein-dev-home/545 as transient_infra_failure (confidence 0.95); first failed gate: scm_checkout_fetch.

Why a human is needed

This build never got past pulling the source: Jenkins' initial checkout (done just to read the Jenkinsfile) tried to fetch from scm.bstein.dev and the Git server returned an HTTP 500 in the middle of listing refs ('fatal: expected flush after ref listing'), so the fetch was cut off and failed. Jenkins retried the checkout and got the same error before giving up. Because the failure happened before any pipeline stage or test ran, there is nothing here that implicates this repository's code, Jenkinsfile, or tests - it's the source-control host itself having trouble serving the request at that moment. There's no code change to make; the expectation is that fetching the same commit succeeds once the Git server side of things is healthy again.

Ariadne did not authorize automated remediation: evidence_signature_missing.

Facts

  • jenkins — Build bstein-dev-home #545 completed with result FAILURE after 154.8s (2026-09-23T04:02:16Z to 2026-09-23T04:04:51Z). (jenkins.result, jenkins.timestamps, jenkins.duration_seconds)
  • jenkins — The failure occurred during the initial lightweight checkout Jenkins performs to read the Jenkinsfile from scm.bstein.dev, before any pipeline stage was defined or run. (jenkins.console_tail: 'Checking out git https://scm.bstein.dev/bstein/bstein-dev-home.git ... to read Jenkinsfile')
  • jenkins — The git fetch against the origin remote failed with 'error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500' and 'fatal: expected flush after ref listing', reported by Jenkins as GitException with git exit status 128. (jenkins.console_failures[0])
  • jenkins — Jenkins retried the checkout and hit the same fetch error again, then aborted: 'ERROR: Maximum checkout retry attempts reached, aborting'. (jenkins.console_tail)
  • jenkins — No pipeline stage was reported as failing (first_failed_stage is null) and no test results were published (failed_tests is empty), consistent with the build never advancing past checkout. (jenkins.first_failed_stage, jenkins.failed_tests)
  • opensearch — OpenSearch log evidence for the incident window could not be retrieved: 'opensearch request failed: [Errno 111] Connection refused'. (log_evidence.error)

Evidence

The earliest failure region of the build console:

	at PluginClassLoader for git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1310)
	at PluginClassLoader for git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277)
	at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136)
	at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:168)
	at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:70)
	at PluginClassLoader for workflow-job//org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:317)
	at hudson.model.ResourceController.execute(ResourceController.java:101)
	at hudson.model.Executor.run(Executor.java:460)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- https://scm.bstein.dev/bstein/bstein-dev-home.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
fatal: expected flush after ref listing

	at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.C
... (truncated; the full log is in the linked build)

Inferences

  • The HTTP 500 and 'fatal: expected flush after ref listing' indicate the Gitea server (or something in front of it) errored out mid-stream while advertising refs to git, rather than git or Jenkins malforming the request.
  • Because this happened during the pre-stage checkout used only to fetch the Jenkinsfile, none of this repository's actual code or tests were exercised in this build - the failure is entirely upstream of anything the pipeline defines.
  • Nothing in the evidence points to a problem with the commit, the Jenkinsfile, or repository content; the same commit would be expected to check out cleanly once the Git server is responding normally again.

Links

Filed automatically by Ariadne from a Hermes Agent diagnosis (run run_c08f002e4be4405fb13ecb98f3ebdba8). Hermes has no write access to this repository; no files or infrastructure were changed.

Hermes auto-triage classified incident `bstein-dev-home/545` as **transient_infra_failure** (confidence 0.95); first failed gate: `scm_checkout_fetch`. ## Why a human is needed This build never got past pulling the source: Jenkins' initial checkout (done just to read the Jenkinsfile) tried to fetch from scm.bstein.dev and the Git server returned an HTTP 500 in the middle of listing refs ('fatal: expected flush after ref listing'), so the fetch was cut off and failed. Jenkins retried the checkout and got the same error before giving up. Because the failure happened before any pipeline stage or test ran, there is nothing here that implicates this repository's code, Jenkinsfile, or tests - it's the source-control host itself having trouble serving the request at that moment. There's no code change to make; the expectation is that fetching the same commit succeeds once the Git server side of things is healthy again. Ariadne did not authorize automated remediation: `evidence_signature_missing`. ## Facts - **jenkins** — Build bstein-dev-home #545 completed with result FAILURE after 154.8s (2026-09-23T04:02:16Z to 2026-09-23T04:04:51Z). (`jenkins.result, jenkins.timestamps, jenkins.duration_seconds`) - **jenkins** — The failure occurred during the initial lightweight checkout Jenkins performs to read the Jenkinsfile from scm.bstein.dev, before any pipeline stage was defined or run. (`jenkins.console_tail: 'Checking out git https://scm.bstein.dev/bstein/bstein-dev-home.git ... to read Jenkinsfile'`) - **jenkins** — The git fetch against the origin remote failed with 'error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500' and 'fatal: expected flush after ref listing', reported by Jenkins as GitException with git exit status 128. (`jenkins.console_failures[0]`) - **jenkins** — Jenkins retried the checkout and hit the same fetch error again, then aborted: 'ERROR: Maximum checkout retry attempts reached, aborting'. (`jenkins.console_tail`) - **jenkins** — No pipeline stage was reported as failing (first_failed_stage is null) and no test results were published (failed_tests is empty), consistent with the build never advancing past checkout. (`jenkins.first_failed_stage, jenkins.failed_tests`) - **opensearch** — OpenSearch log evidence for the incident window could not be retrieved: 'opensearch request failed: [Errno 111] Connection refused'. (`log_evidence.error`) ## Evidence The earliest failure region of the build console: ``` at PluginClassLoader for git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1310) at PluginClassLoader for git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277) at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136) at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:168) at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:70) at PluginClassLoader for workflow-job//org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:317) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:460) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- https://scm.bstein.dev/bstein/bstein-dev-home.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 fatal: expected flush after ref listing at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.C ... (truncated; the full log is in the linked build) ``` ## Inferences - The HTTP 500 and 'fatal: expected flush after ref listing' indicate the Gitea server (or something in front of it) errored out mid-stream while advertising refs to git, rather than git or Jenkins malforming the request. - Because this happened during the pre-stage checkout used only to fetch the Jenkinsfile, none of this repository's actual code or tests were exercised in this build - the failure is entirely upstream of anything the pipeline defines. - Nothing in the evidence points to a problem with the commit, the Jenkinsfile, or repository content; the same commit would be expected to check out cleanly once the Git server is responding normally again. ## Links - Failed build: https://ci.bstein.dev/job/bstein-dev-home/545/ - Full evidence bundle and audit trail live in Ariadne at `/api/admin/audit/events`, event types `hermes_autotriage_incident` and `hermes_autotriage_diagnosis`. Filed automatically by Ariadne from a Hermes Agent diagnosis (run [run_c08f002e4be4405fb13ecb98f3ebdba8](https://triage.bstein.dev/chat?resume=run_c08f002e4be4405fb13ecb98f3ebdba8)). Hermes has no write access to this repository; no files or infrastructure were changed. <!-- hermes-triage job=bstein-dev-home classification=transient_infra_failure incident=bstein-dev-home/545 -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bstein
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bstein/bstein-dev-home#81
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?