@RobertoSchneiders We recently fixed this issue too.
Perhaps you have the same cause: are you not pinning the patch version of erlang in your CI?
Here is the cause breakdown from our bug ticket:
- Dialyzer creates an md5 hash of files to check, and that includes beam files.
- We are not pinning an exact version of erlang in CI
- Prior to each failing PLT check has been an erlang patch version bump!
- It looks like erlang project releases the patch bumps roughly weekly. This explains the roughly-weekly occurences we were seeing. It wasn’t a timestamp issues as first suspected.
- This patch bump means that the PLT files are different to the ones in the cache, so dialyzer is correctly flagging the old PLT files.
Proposed solution: check
.tool-versionsduring CI setup and install the exact pinned version of erlang that our project uses.
Note: I also included the erlang version in the cache key, to avoid confusion in future and to immediately bust the cache lookup.
