Commit 6bc407abfbb for woocommerce

commit 6bc407abfbbb9dbfa0160be3b061ceb98dc118a6
Author: Adrian Moldovan <3854374+adimoldovan@users.noreply.github.com>
Date:   Fri Jul 10 17:51:39 2026 +0300

    Classify wp-env-start 'socket hang up' retries as reason=wordpress (#66501)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index ad64c9f9fe5..34085a60eaf 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -203,7 +203,7 @@ jobs:
         if: ${{ matrix.testEnv.shouldCreate }}
         # `wp-env start` fails on transient network timeouts from several subsystems:
         # composer fetching packagist inside the Docker build ("curl error 28"), wp-env's
-        # own `got` client downloading WordPress core ("ETIMEDOUT"), and the Docker daemon
+        # own `got` client downloading WordPress core ("ETIMEDOUT"/"socket hang up"), and the Docker daemon
         # pulling images from Docker Hub ("context deadline exceeded"). Retry the whole
         # start to ride out those blips -- BuildKit reuses layers that already succeeded,
         # so a retry only re-runs whatever failed. Each retried attempt emits a
@@ -220,7 +220,7 @@ jobs:
             # patterns below, so reason= is for monitoring only, not a retry gate.
             if grep -qF 'curl error 28' "$log"; then reason=packagist
             elif grep -qE 'registry-1\.docker\.io|context deadline exceeded' "$log"; then reason=dockerhub
-            elif grep -qF 'ETIMEDOUT' "$log"; then reason=wordpress
+            elif grep -qE 'ETIMEDOUT|socket hang up|ECONNRESET' "$log"; then reason=wordpress
             else reason=unknown
             fi
             if [ "$attempt" -ge "$max_attempts" ]; then