Github e2e ci always failed in recent weeks. #505
Description
What happened:
The pipeline has started failing unexpectedly in recent weeks. Previously stable workflows now encounter errors during execution, with no intentional changes made to the related code or configuration on our side.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Trigger the CI pipeline via the standard trigger (e.g., push code to the target branch, create a pull request).
Observe the pipeline execution in the GitHub Actions interface.
The failure consistently occurs at the same stage(s) of the workflow (adjust if specific: e.g., "dependency installation" or "test execution") across multiple runs.
Anything else we need to know?:
This issue only emerged in the past 2-3 weeks. We suspect it may be related to recent changes in the GitHub environment (e.g., updates to GitHub Actions runners, deprecated dependencies, or changes to environment variables/access permissions).
Environment:
- Kubernetes version (use
kubectl version): - llmaz version (use
git describe --tags --dirty --always): - Cloud provider or hardware configuration:
- OS (e.g:
cat /etc/os-release): - Kernel (e.g.
uname -a): - Install tools:
- Others: