CI: `tls` failing in the nightly

[github-actions]

tls is failing in the nightly — 3 night(s) running, since 2026-09-09.

High · runtime-failure · affects this-dir

• Symptom — Builds run but client fails to load CA (ret -151) and server accept fails with -308 over 3 nights on both refs
• Likely cause — CA certificate load fails at runtime (ASN error -151), not an expiry (-155); likely a cert/fixture or example issue affecting handshake
• Next — Investigate the CA cert being loaded and the -151 ASN error in the tls example; verify fixture validity and load path

What failed

test	wolfSSL	error
./server-tls + ./client-tls-pkcs12	master	client rc=25
./server-tls + ./client-tls-pkcs12	v5.9.2-stable	client rc=25

log tail

--- client ---
Read 4328 bytes from file
Failed to load CA. ret = -151

--- server ---
Waiting for a connection...
wolfSSL_accept error = -308
--- client ---
Read 4328 bytes from file
Failed to load CA. ret = -151

--- server ---
Waiting for a connection...
wolfSSL_accept error = -308

---

Filed automatically by ci-triage. Body updated 2026-09-11 UTC.
Add the ci:mute label to stop all updates. Closing as not planned prevents reopening.

[github-actions]

Night 2 · run · 2026-09-10

Real — retried once, failed again.

High · Client builds but fails at runtime: 'Failed to load CA. ret = -151' and server aborts with wolfSSL_accept error -308
next: Inspect the certs/ CA file the tls example loads and reproduce cert parse error -151 locally to determine if fixture is malformed or unsupported

Failing on: master, v5.9.2-stable

[github-actions]

Night 3 · run · 2026-09-11

Real — retried once, failed again.

High · Builds run but client fails to load CA (ret -151) and server accept fails with -308 over 3 nights on both refs
next: Investigate the CA cert being loaded and the -151 ASN error in the tls example; verify fixture validity and load path

Failing on: master, v5.9.2-stable