Don't store the qt5-declarative port in the GitHub Action cache

[wy-luke]

Describe the bug
When running in github action macos-latest environment, vcpkg don't store the qt5-declarative port in the GitHub Action cache. Every time it will be rebuilt and took much time to finish.

The logs:

-- Installing: ......./vcpkg/packages/qt5-declarative_x64-osx/share/qt5-declarative/copyright
-- Performing post-build validation
Stored binaries in 0 destinations.
Elapsed time to handle qt5-declarative:x64-osx: 33 min

All other packages were cached except the qt5-declarative.

But it could be cached locally in .cache/vcpkg folder in my mac.

I used the run-vcpkg action and the author think it's vcpkg issue. So I report it here.
lukka/run-vcpkg#200

Environment

• OS: Github action macos-latest environment. My local environment is OSX_13

To Reproduce
My github action workflow

Expected behavior
Create and store cache for qt5-declarative and use that cache in later actions.

Failure logs
After installed the log shows:

Stored binaries in 0 destinations.

My workflow full log

[LilyWangLL]

Thanks for posting this issue. The issue title and your description show qt5-declarative created cache after install succeed. But your Expected behavior is Vcpkg don't store the qt5-declarative port in the GitHub Action cache.

Which is your expected result? Do you want qt5-declarative to generate cache after installation?

[wy-luke]

Thanks for posting this issue. The issue title and your description show qt5-declarative created cache after install succeed. But your Expected behavior is Vcpkg don't store the qt5-declarative port in the GitHub Action cache.

Which is your expected result? Do you want qt5-declarative to generate cache after installation?

@LilyWangLL My fault. I thought it was expected failure result...😂

The expected successful result is to create and store cache for qt5-declarative and use that cache in later actions.

I have edited it. Thanks.

[autoantwort]

Sounds like #31072 since both packages are large.

[wy-luke]

Sounds like #31072 since both packages are large.

@autoantwort Yeah, I also strongly suspect that this is the reason. This package is 2GB or so.

However, I couldn't find any error message or log to confirm it.

[github-actions]

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.