[CE] add ce log analysis

[zjjlivein]

Before submitting

• Lint code. If there are lint issues, please format the code first.

# Install and register `pre-commit` in the project folder
pip install pre-commit && pre-commit install

# Process previous code files separately
pre-commit run --file XXXX.py

• Add test cases into tests folder. If there are codecov issues, please add tests cases first.

PR types

PR changes

Description

[paddle-bot]

Thanks for your contribution!

[Paddle-CI-Bot]

PaddleFormers Log Analysis

Run #26215444743 · Attempt 1

日志分析报告

流水线名称	问题标签	修复建议
CI_ILUVATAR	环境问题（container failed）	自定义容器启动失败，建议 CI 维护人员检查 Runner iluvatar-gpu-2-nczzk-runner-jpzdf 的 Docker 配置及资源状态后 rerun。

失败的测试case:

无测试 case 执行（全部 skipped）

失败步骤：Print current runner name
  - 错误：failed to run script step: [object Object]
  - 错误：Process completed with exit code 1
  - 错误：Executing the custom container implementation failed.
           Please contact your self hosted runner administrator.

后续步骤（因上述失败全部跳过）：
  - Checkout code         → skipped
  - Merge PR (if needed)  → skipped
  - Run CI unittest       → skipped

根本原因分析:

PR #4503（add_ce_log_analysis）仅修改了 .github/workflows/formers_bot_analysis.yml，未触及任何模型代码或测试脚本，排除 PR 代码变更导致失败的可能。

失败根因为 Runner 侧容器环境异常：

• Runner：iluvatar-gpu-2-nczzk-runner-jpzdf（天数机器）
• 容器在 Print current runner name 阶段（curl 代理连通性检测后）启动失败，返回 exit code 1
• 错误信息 Executing the custom container implementation failed 明确指向自定义 K8s 容器执行器（/home/runner/k8s/index.js）异常，而非业务逻辑问题

修复建议:

1. 联系 CI 维护人员检查 Runner iluvatar-gpu-2-nczzk-runner-jpzdf 的 K8s Pod 状态及 Docker 容器配置是否正常
2. 确认天数机器资源（GPU/内存）未被占满，排除资源不足导致容器拉起失败
3. 环境确认正常后直接 rerun 该 job，无需修改 PR 代码

---

_{🔄 每次 Re-run 后自动更新}