Cleaning

Author: marcin-cebo

.github/workflows/run-tests.yml

@@ -60,86 +60,6 @@ jobs:
         run: |
           composer self-update && composer --version
           composer install --prefer-dist
-      # TEMPORARY: diagnose intermittent `cURL error 28` timeouts to ps.pndsn.com
-      # from the self-hosted runner. Remove once the runner egress issue is resolved.
-      - name: Diagnose ps.pndsn.com connectivity
-        continue-on-error: true
-        run: |
-          echo "=== Runner public egress IP ==="
-          curl -s --max-time 15 https://api.ipify.org || echo "(could not determine egress IP)"
-          echo
-          echo "=== DNS resolution for ps.pndsn.com ==="
-          getent hosts ps.pndsn.com || nslookup ps.pndsn.com || true
-          echo
-          echo "=== Proxy-related environment ==="
-          env | grep -iE 'proxy' || echo "(no proxy env vars set)"
-          echo
-          echo "=== 10x probe of https://ps.pndsn.com/time/0 (catch intermittent hang) ==="
-          for i in $(seq 1 10); do
-            echo "--- attempt $i ---"
-            curl -sS -o /dev/null --max-time 15 \
-              -w 'http_code=%{http_code} dns=%{time_namelookup}s connect=%{time_connect}s tls=%{time_appconnect}s total=%{time_total}s\n' \
-              "https://ps.pndsn.com/time/0" \
-              || echo "attempt $i FAILED (curl exit $?)"
-          done
-          echo
-          echo "=== Burst probe A: 200x time/0, 20 concurrent (keyless baseline) ==="
-          # Cheap, unauthenticated endpoint. Establishes that the network path is fine
-          # under concurrent load. time/0 is NOT subject to per-key publish throttling.
-          burst_log="$(mktemp)"
-          seq 1 200 | xargs -P 20 -I {} \
-            curl -sS -o /dev/null --max-time 15 \
-              -w 'http_code=%{http_code} total=%{time_total}s\n' \
-              "https://ps.pndsn.com/time/0" \
-            >> "$burst_log" 2>&1 || true
-          echo "--- HTTP status code distribution ---"
-          grep -oE 'http_code=[0-9]+' "$burst_log" | sort | uniq -c || true
-          echo "--- slowest 5 ---"
-          sort -t= -k3 -rn "$burst_log" | head -5 || true
-          echo
-          echo "=== Burst probe B: 200x PUBLISH, 20 concurrent (the actual failing op) ==="
-          # Publishes to the real keyset — the same operation that times out in CI.
-          # If THIS bursts shows 429 / 000 / ~10s stalls while probe A stayed fast,
-          # the cause is per-key publish throttling, not the network or the runner.
-          pub_log="$(mktemp)"
-          seq 1 200 | xargs -P 20 -I {} \
-            curl -sS -o /dev/null --max-time 15 \
-              -w 'http_code=%{http_code} total=%{time_total}s\n' \
-              "https://ps.pndsn.com/publish/$PUBLISH_KEY/$SUBSCRIBE_KEY/0/diag-burst/0/%22x%22?uuid=diag-burst" \
-            >> "$pub_log" 2>&1 || true
-          echo "--- HTTP status code distribution ---"
-          grep -oE 'http_code=[0-9]+' "$pub_log" | sort | uniq -c || true
-          echo "--- non-200 / slow (>1s) responses ---"
-          grep -E 'http_code=(000|4|5)|total=[1-9]' "$pub_log" || echo "(none — all fast 200s)"
-          echo "--- slowest 5 ---"
-          sort -t= -k3 -rn "$pub_log" | head -5 || true
-      # TEMPORARY: raw `curl` CLI control that reuses ONE keep-alive connection
-      # across many publishes (one curl process, N urls via -K). This is the
-      # PHP-free reproducer for the server team: if it hangs every ~10th here on
-      # the dense CI runner, the every-10th black-hole is reproducible with no
-      # PHP/Guzzle/SDK involvement at all. Locally (high RTT) it ran 200/200
-      # clean — this step tests it on the same runner/pool that fails for Guzzle.
-      # Remove once the timeout cause is confirmed/fixed.
-      - name: Diagnose connection reuse (raw curl CLI)
-        continue-on-error: true
-        run: |
-          curl --version | head -1
-          DIAG_ITERATIONS=200 ./scripts/diag-curl.sh
-      # TEMPORARY: PHP-level probe that REUSES one Guzzle client across many
-      # requests, exactly like the SDK does for a whole PHPUnit run. The curl
-      # probes above open a fresh connection each time and so cannot reproduce a
-      # stale/half-closed keep-alive socket — the prime suspect for
-      # "connected fine, then 0 bytes received after 10s" (cURL error 28).
-      # DIAG_DELAY_MS inserts an idle gap to provoke LB idle-timeout of pooled
-      # sockets. Remove once the timeout cause is confirmed/fixed.
-      - name: Diagnose Guzzle connection reuse (PHP)
-        continue-on-error: true
-        run: |
-          # Reuses one Guzzle client like the SDK. The keyless time/0 baseline
-          # should be 0 failures; the publish run reproduces the cURL-28 timeout.
-          # The built-in spacing sweep then tells us whether spacing publishes
-          # further apart makes the failures disappear (== server rate limit).
-          DIAG_ITERATIONS=200 DIAG_DELAY_MS=0 php scripts/diag-guzzle.php
       - name: Run unit tests
         run: composer test
       - name: Cancel workflow runs for commit on error