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

Browse Source

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.

...

This commit is contained in:

yhirose

2026-07-23 18:55:41 -04:00

parent cc1be5ebb5

commit f7c8455a62

1 changed files with 415 additions and 415 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

test/test.cc

+415 -415

File diff suppressed because it is too large Load Diff