CI: `bsdkm` failing in the nightly

[github-actions]

bsdkm is failing in the nightly — 5 night(s) running, since 2026-09-16.

Medium · unknown · affects this-dir

• Symptom — No log captured for bsdkm build against master; cannot determine failure
• Likely cause — Log output missing or truncated; failing 5 consecutive nights suggests a persistent issue but no evidence available
• Next — Re-run with log capture enabled and inspect bsdkm build output directly

What failed

test	wolfSSL	error
bsdkm	master	job failed

---

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

[github-actions]

Night 2 · run · 2026-09-17

Real — retried once, failed again.

Medium · No log captured; cannot determine failure cause for bsdkm on both master and v5.9.2-stable
next: Re-run job with log capture enabled or inspect CI artifact for bsdkm build output

Failing on: master, v5.9.2-stable

[github-actions]

Night 3 · run · 2026-09-17

Real — retried once, failed again.

Medium · No log captured; cannot determine failure cause for bsdkm example
next: Re-run with log capture enabled or inspect CI artifacts for bsdkm build output

Failing on: master

[github-actions]

Night 4 · run · 2026-09-18

Real — retried once, failed again.

Medium · No log captured; cannot determine failure cause for bsdkm example
next: Re-run job with log capture enabled to obtain build/test output for bsdkm

Failing on: master

[github-actions]

Night 5 · run · 2026-09-19

Real — retried once, failed again.

Medium · No log captured for bsdkm build against master; cannot determine failure
next: Re-run with log capture enabled and inspect bsdkm build output directly

Failing on: master