Skip to content

Conversation

@firewave
Copy link
Collaborator

No description provided.


# TODO: is this actually applied to the guest?
env:
# TODO: figure out why there are cache misses with PCH enabled
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It turns out this was working just fine in this workflow although we forgot to disable the precompiled headers. So we should be able to enable them in the other jobs as well.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The first run also got cache hits which was unexpected. Turns out we are lacking the branch name in the cache key which causes it to be used across all builds (IIRC I assumed the cache is limited to the branch). So any PR will affect the cache of main builds.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also create a new cache with each build because it automatically appends a timestamp. That is done to prevent issues with concurrent access (see hendrikmuhs/ccache-action#117). It seems that might not be necessary for branches but since multiple pushes trigger multiple builds we cannot disable this. That would require us to cancel the already running builds (see https://trac.cppcheck.net/ticket/12325).

@firewave firewave changed the title fixed #13788 - CI-unixish-docker.yml: replaced ubuntu:24.10 with ùbuntu:25.04 / cleanups fixed #13788 - CI-unixish-docker.yml: replaced ubuntu:24.10 with ubuntu:25.04 / cleanups Apr 18, 2025
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.

1 participant