From db6c9ef27bba3d5fcbc434966534be47c9070bd0 Mon Sep 17 00:00:00 2001 From: yhirose Date: Wed, 29 Apr 2026 10:38:45 +0900 Subject: [PATCH] Drop mbedTLS continue-on-error now that the matrix is stable With the close_notify mid-response fix and SHARDS=2 mitigation, the mbedTLS legs run reliably on both ubuntu and macos. Drop the continue-on-error escape hatch so future regressions actually break the build. Co-Authored-By: Claude Opus 4.7 (1M context) --- .github/workflows/test.yaml | 6 ------ 1 file changed, 6 deletions(-) diff --git a/.github/workflows/test.yaml b/.github/workflows/test.yaml index 0a20596..7b97b84 100644 --- a/.github/workflows/test.yaml +++ b/.github/workflows/test.yaml @@ -80,10 +80,6 @@ jobs: fail-fast: false matrix: tls_backend: [openssl, mbedtls, wolfssl] - # TODO: mbedTLS jobs hit pre-existing flaky failures (timing-sensitive - # ServerTest cases under ASAN+mbedTLS). Allow them to fail without - # blocking until the underlying flakiness is investigated. - continue-on-error: ${{ matrix.tls_backend == 'mbedtls' }} name: ubuntu (${{ matrix.tls_backend }}) steps: - name: checkout @@ -221,8 +217,6 @@ jobs: fail-fast: false matrix: tls_backend: [openssl, mbedtls, wolfssl] - # See ubuntu job above. - continue-on-error: ${{ matrix.tls_backend == 'mbedtls' }} name: macos (${{ matrix.tls_backend }}) steps: - name: checkout