Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Windows CI: parallel vcpkg z-applocal steps fail with file lock

未關閉
#944 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 3 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
45/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
cpp

研究方向

Start with the linked Windows CI run and the Build Iceberg step, then inspect the build configuration that invokes vcpkg z-applocal for targets such as parquet_test.exe. Reproduce the parallel linking failure and determine which shared dependency file is locked; done means the Windows CI job completes reliably without z-applocal file-lock errors.

由索引模型根據 Issue 內容生成。

描述

Summary

The Windows CI job fails during the Build Iceberg step because a post-link vcpkg z-applocal command cannot access a file that is locked by another process.

Failure details

Run:
https://github.com/apache/iceberg-cpp/actions/runs/35413148123/job/105816560819

The build reaches 955/958 targets. Compilation succeeds, but linking parquet_test.exe fails while running:

vcpkg.exe z-applocal
  --target-binary=.../build/src/iceberg/test/parquet_test.exe
  --installed-bin-dir=C:/vcpkg/installed/x64-windows/debug/bin

The reported error is:

The process cannot access the file because it is being used by another process.

Ninja then stops with exit code 1. The exact locked file is not reported.

Suspected cause

Multiple Windows test targets are linked in parallel, and their post-link z-applocal steps may concurrently copy or access the same dependency DLLs.

This appears to be a Windows build/deployment race rather than a C++ compile failure. The compiler reported zero compilation failures.

Possible fixes

  • Serialize the z-applocal post-link steps on Windows.
  • Use a target-specific dependency copy directory.
  • Add a bounded retry for transient file-lock failures.
  • Disable automatic applocal deployment for test targets and copy dependencies once after the build.
主要語言
C++
星號
230
分支
138
平均合併
4 天 12 小時
30 天內合併 PR
65

環境準備

這個專案沒有提供開發容器、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 摘要。