-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ci upload cache] upload cache failure #44060
Comments
20250121.1 cb47618 https://dev.azure.com/vcpkg/public/_build/results?buildId=111706&view=logs&j=f79cfdd7-47a8-597f-8f57-dc3e21a8f2ad&t=4f03addf-ef5a-50a2-71be-19894d9df4e3&l=29994
# vcpkg install llvm[clang,compiler-rt,core,default-targets,enable-abi-breaking-checks,enable-bindings,enable-eh,enable-rtti,enable-terminfo,enable-zlib,enable-zstd,libc,libclc,lld,lldb,target-x86,tools]
# du -hs packages/llvm_x64-linux/
25G packages/llvm_x64-linux/
# du -hs packages/llvm_x64-linux/debug/lib/* | sort -hk1 | tail
470M packages/llvm_x64-linux/debug/lib/libLLVMAnalysis.a
681M packages/llvm_x64-linux/debug/lib/libclangAST.a
968M packages/llvm_x64-linux/debug/lib/libclangSema.a
1.1G packages/llvm_x64-linux/debug/lib/libLLVMCodeGen.a
1.2G packages/llvm_x64-linux/debug/lib/libLTO.so.18.1
1.3G packages/llvm_x64-linux/debug/lib/libclangCodeGen.a
1.6G packages/llvm_x64-linux/debug/lib/libclang.so.18.1.6
1.6G packages/llvm_x64-linux/debug/lib/libclangStaticAnalyzerCheckers.a
2.7G packages/llvm_x64-linux/debug/lib/liblldb.so.18.1.6
3.0G packages/llvm_x64-linux/debug/lib/libclang-cpp.so.18.1
# du -h BINARY_CACHE/56/56********.zip
7.1G BINARY_CACHE/56/56********.zip Reference
|
@JavierMatosD Would you please look into this issue? |
Operating system
vcpkg ci
Compiler
No response
Steps to reproduce the behavior
Failure logs
warning: curl failed to put file to https://vcpkgbinarycachewus.blob.core.windows.net/cache/8bfe6e0d14ad4b3dbe12decb3cfe0b64acefdb655e0688c84840c749f776a8a4.zip?*** SECRET *** with exit code 0 and http code 413.
Additional context
Can you check the size of the file before upload it? if the size is too big from the storage, please skip it, and save time.
Alternative you can set a new flag for user that can set upload file max size limit, that if the binary is more that this size, it will skip upload, and set the correct size in the ci.
If this flag is not set, it will be the current behavior without limit.
The text was updated successfully, but these errors were encountered: