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) <noreply@anthropic.com>
This commit is contained in:
yhirose
2026-04-29 10:38:45 +09:00
parent 887837c65b
commit db6c9ef27b

View File

@@ -80,10 +80,6 @@ jobs:
fail-fast: false fail-fast: false
matrix: matrix:
tls_backend: [openssl, mbedtls, wolfssl] 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 }}) name: ubuntu (${{ matrix.tls_backend }})
steps: steps:
- name: checkout - name: checkout
@@ -221,8 +217,6 @@ jobs:
fail-fast: false fail-fast: false
matrix: matrix:
tls_backend: [openssl, mbedtls, wolfssl] tls_backend: [openssl, mbedtls, wolfssl]
# See ubuntu job above.
continue-on-error: ${{ matrix.tls_backend == 'mbedtls' }}
name: macos (${{ matrix.tls_backend }}) name: macos (${{ matrix.tls_backend }})
steps: steps:
- name: checkout - name: checkout