[CI] Improve dependency download reliability and Windows example build isolation

未关闭
#1,101 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
cpp, github-actions

调研方向

Start with the CI workflow steps that download nanoarrow, Boost, and Thrift, then inspect the Windows C++23 example build and sccache setup/finalization. The issue lists transient download failures and a busy shared example/build directory; determine which follow-up to tackle and reproduce it in the relevant CI job. Done means the selected failure mode is addressed and the affected job completes reliably.

由索引模型根据 Issue 内容生成。

描述

help wanted

Recent main-branch CI failures are concentrated in dependency downloads and Windows file contention.

Recurring dependency failures:

  • nanoarrow 0.9.0 downloads from archive.apache.org failed in three Test runs. The latest Windows retry still failed after exhausting download retries.
  • Boost 1.88.0 downloads returned HTTP 504 on Ubuntu and macOS. The Ubuntu retry passed; the macOS failure remains in the run.
  • A Windows SQL Catalog run failed while downloading Thrift 0.22.0 and passed on retry.

Separately, the Windows C++23 example step failed because example/build remained busy after three cleanup attempts.

Possible follow-ups:

  • Improve source/binary caching and download fallback handling, with bounded retries for transient failures.
  • Investigate separate example build directories for each C++ standard.
  • Skip sccache finalization when setup did not complete, avoiding secondary “command not found” errors.
主要语言
C++
星标
227
派生
142
平均合并
3 天 21 分钟
30 天内合并 PR
70

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/iceberg-cpp 的其他 Issue

查看 apache/iceberg-cpp 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。