Skip to content

Conversation

@taeold
Copy link
Contributor

@taeold taeold commented Jul 24, 2025

Summary

  • Increased startDelay from 1 to 5 seconds for all ASGI conformance test steps
  • This matches the configuration used in buildpack integration tests which run reliably

Problem

The ASGI conformance tests are failing sporadically with connection refused errors:

2025/07/24 17:30:27 validation failure: failed to get response from HTTP function: failed to send HTTP request: Post "http://localhost:8080": dial tcp [::1]:8080: connect: connection refused Server logs: [/tmp/ff_serverlog_stdout.txt]: '' [/tmp/ff_serverlog_stderr.txt]: '' 

Hypothesis

The default 1-second start delay may be insufficient for Uvicorn/ASGI server startup in CI environments.

Seems to be more stable w/ this change.
image

@taeold taeold force-pushed the fix-asgi-conformance-flaky-test branch from fc005ab to 18c1141 Compare July 24, 2025 19:41
… failures The ASGI conformance tests are failing sporadically with connection refused errors, where the server appears to not be ready when the test client attempts to connect. Hypothesis: The default 1-second start delay may be insufficient for Uvicorn/ASGI server startup in CI environments. This change increases startDelay to 5 seconds to match the buildpack integration tests, which have been running reliably. Note: The GitHub Action expects startDelay (camelCase) as an input parameter, which it then passes to the conformance test client as -start-delay flag. This is an attempt to diagnose and fix the intermittent failures - further investigation may be needed if the issue persists.
@taeold taeold force-pushed the fix-asgi-conformance-flaky-test branch from 18c1141 to 61c4362 Compare July 24, 2025 19:46
@akerekes akerekes merged commit 1b6c428 into GoogleCloudPlatform:main Jul 24, 2025
71 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants