Skip to content

[gcs] Bump according to https://github.com/duckdb/community-extensions/pull/1341#1536

Open
carlopi wants to merge 1 commit intomainfrom
carlopi-patch-gcs
Open

[gcs] Bump according to https://github.com/duckdb/community-extensions/pull/1341#1536
carlopi wants to merge 1 commit intomainfrom
carlopi-patch-gcs

Conversation

@carlopi
Copy link
Collaborator

@carlopi carlopi commented Mar 16, 2026

@russellhancox and @fb64: this is an attempt at CI debugging the bump of gcs, lets' see.

@carlopi carlopi mentioned this pull request Mar 16, 2026
@fb64
Copy link

fb64 commented Mar 16, 2026

The file D:\a\community-extensions\community-extensions\vcpkg\buildtrees\google-cloud-cpp\x64-windows-static-release-rel\external\googleapis\google\iam\credentials\v1\iamcredentials.grpc.pb.cc seems to be not accessible or present CF L693 but the step that generate this file just before have been worked CF L661
Could be a path length issue or something similar ? Is it possible to inspect the working directory of the worker ?

@fb64
Copy link

fb64 commented Mar 17, 2026

@carlopi, I really think it due to a path related issue (too long or something else)...
I performed some test on my fork.
I put the same commit with just the windows_amd64 target enabled, the first build failed as in community-extensions repo (same error on vcpkg google-cloud-cpp build), then I renamed the my fork repository to co-ex instead of community-extensions in order to shorten the path. I relaunched the previous failed build (in debug) and it finally passed 🎉 ….
A possible solution could to set vcpkgDirectory variable here with a shorten path D:\a\vcpkg for example.But I'm not sure if this change requires any further adjustments …
Another one would be to enabe long path in windows on the windows worker...
Hope I would help you to fix this.

@fb64
Copy link

fb64 commented Mar 18, 2026

Full build with all platforms has been passed as well : https://github.com/fb64/co-ex/actions/runs/23231852913

@fb64
Copy link

fb64 commented Mar 19, 2026

Hi @carlopi, I tried a modified version of extension-ci-tools with this commit to shorten the vcpkg path and it's working well on my fork !
Should I open an issue and a pull request on extension-ci-tools to propose this fix ?

@fb64
Copy link

fb64 commented Mar 19, 2026

For more details, I think the two following files used during the vcpkg process that exceed 260 characters are responsible of this error:

  • 261 --> D:\a\community-extensions\community-extensions\vcpkg\buildtrees\google-cloud-cpp\x64-windows-static-release-rel\external\googleapis\CMakeFiles\google_cloud_cpp_iam_credentials_v1_iamcredentials_protos.dir\google\iam\credentials\v1\iamcredentials.grpc.pb.cc.obj
  • 267 --> D:\a\community-extensions\community-extensions\vcpkg\buildtrees\google-cloud-cpp\x64-windows-static-release-rel\external\googleapis\CMakeFiles\google_cloud_cpp_iam_credentials_v1_iamcredentials_protos.dir\google_cloud_cpp_iam_credentials_v1_iamcredentials_protos.pdb

Those 2 files in the main respository are under 260 characters due to the repo name: community-extensions\community-extensions --> duckdb-gcs\duckdg-gcs and therefore the build pass ....

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.

2 participants