Tracking: Known pre-existing CI test failures

[deyaaeldeen]

Purpose

This issue tracks known, pre-existing CI test failures that are caused by infrastructure, service-side, or external dependency issues — not by code bugs in this repository. The automated Analyze CI Test Failures workflow uses this issue to skip known failures and avoid filing duplicate issues.

Known Failures

No known CI (playback) failures at this time.

Note: This list only tracks failures from CI pipelines (ci.yml, playback mode). Live-test pipeline failures (tests.yml) are excluded — the workflow filters them out by check-run name.

Maintenance Guidelines

• Adding entries: When a CI failure is confirmed to be a pre-existing infrastructure/service issue (not a code bug), add it here with the package name, test pattern, error summary, root cause, and a tracking issue link.
• Removing entries: When the underlying issue is fixed and CI is green again, remove the entry and close the corresponding tracking issue.
• Format: Each entry must include the package name (as it appears in check-run names) so the workflow can match it.
• Review cadence: Review this list monthly to check if any known failures have been resolved.