Skip to content

fix(ci): give GTK dependency installs bounded unpacking headroom - #72

Closed
efeire wants to merge 1 commit into
mainfrom
fix/ci-gtk-dependency-timeout
Closed

efeire wants to merge 1 commit into
mainfrom
fix/ci-gtk-dependency-timeout

Conversation

@efeire

@efeire efeire commented Oct 22, 2026 •

Copy link
Copy Markdown
Owner

变更说明 / Summary

为 Linux GTK/WebKit 系统依赖安装保留完成下载后的解包时间。

 apt-get update: 10 分钟(不变)
-GTK/WebKit apt-get install: 10 分钟
+GTK/WebKit apt-get install: 20 分钟
 网络读取: 30 秒;重试: 3 次;超时后强制终止: 30 秒(不变)

仅调整 packages、rust-fmt-clippy、rust-test 三处同类安装。Agent 的较小依赖安装仍为 10 分钟;不改测试、feature、作业选择或成功判据。

变更类型 / Change Type

  • CI / 构建 / CI or build

验证 / Evidence

  • Before: 原生 Job PR 的 Clippy job 在系统依赖安装阶段退出 124:下载持续接近 10 分钟,刚开始读取 dpkg 数据库就被总时限截断,未执行 Clippy。
  • After: 更新现有 workflow 合同测试,核对各 job 的独立 update/install 上限;先见 RED,再使定向测试通过。原 30 秒网络超时、3 次重试和 kill-after 均保留。
  • node --test --test-name-pattern="Linux Rust dependency installs" .github/scripts/ci-workflow.test.mjs
  • git diff --check
  • fork 精确 SHA 88caa5c6fa 的完整 CI 39875344621:50 个 job 成功、JDBC 独立 job 按范围跳过、零失败 step;包含完整 workspace Rust 测试/Clippy、packages 发布 dry-run、Windows/Win7、Nix 和 Agent 矩阵。
  • 上游同 SHA CI 39878484238 完成:50 个 job 成功、JDBC 独立 job 按范围跳过、零失败 step;依赖安装步骤实际成功(该步骤包含 update 和 install,共 13 分 2 秒),后续 Clippy、完整 workspace 测试及打包检查均通过。

Windows 上整份 workflow 测试含既有 LF 正则及 Bash 启动用例,未全过;本次不改这些无关入口,完整测试交 Linux CI。实际慢速镜像条件不在本机模拟,20 分钟仍是明确上限,不保证任意镜像速度均可成功。

Merge Danger

Door: two-way

Blast Radius: CI。最坏增加三类 GTK/WebKit 安装失败前的等待上限,不改变产品运行行为。

关联 Issue / Related Issue

Related t8y2#13201。独立 CI 修复,不混入原生 Job 功能 PR;未修改没有本次失败证据的 TDengine 路径。

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-23T00:01:23.067425Z 88caa5c PR opened
🔒 Security Review ✅ Completed 2026-10-23T00:04:44.055134Z 88caa5c PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant