Skip to content

Log res.error() on all ServerTest ASSERT_TRUE(res) assertions#2507

Merged
yhirose merged 1 commit into
masterfrom
flaky-ci-diagnostics
Jul 24, 2026
Merged

Log res.error() on all ServerTest ASSERT_TRUE(res) assertions#2507
yhirose merged 1 commit into
masterfrom
flaky-ci-diagnostics

Conversation

@yhirose

@yhirose yhirose commented Jul 23, 2026

Copy link
Copy Markdown
Owner

Summary

  • Only 8 of 423 ASSERT_TRUE(res) call sites in test.cc logged the actual error on failure
  • The MbedTLS-backend flaky CI failure (connection-level ASSERT_TRUE(res), ~20-30ms, tracked across GetWithRange4/5, TooLongRequest, UserDefinedMIMETypeMapping) keeps landing on assertions without this diagnostic, so the real error code has never been captured
  • Broadens the existing GetWithRange-only logging (a4d7066) to every plain ASSERT_TRUE(res); site — no behavior change, purely diagnostic

Test plan

  • make test_mbedtls — all 736 tests pass locally
  • make test_split_mbedtls — split build compiles cleanly
  • Watch for the next MbedTLS-backend flake in CI and read the logged error code

Only 8 of 423 call sites logged the actual error on failure. The
MbedTLS-backend flaky CI failure (connection-level ASSERT_TRUE(res),
~20-30ms) keeps landing on assertions without this diagnostic, so the
real error code has never been captured. Broadens the existing
GetWithRange-only logging (a4d7066) to every plain ASSERT_TRUE(res);
site, no behavior change.
@yhirose
yhirose merged commit 82b1492 into master Jul 24, 2026
59 of 61 checks passed
@yhirose
yhirose deleted the flaky-ci-diagnostics branch July 24, 2026 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant