-
Notifications
You must be signed in to change notification settings - Fork 52
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
Missing dialyzer types file after update to 1.16.0 release #214
Comments
Yeah I'm seeing this as well. I'm currently working around it by using v1.15.4:
|
Not sure where this issue is coming from. Can you create an example repo. that replicates the issue? Our CI is passing, so it's either incomplete or it's some other edge case we'll need to handle. |
In the meantime, if you want, you can add to our test cases a replica or your inputs, to see if the error surfaces, here. |
Also, maybe related to jeremyjh/dialyxir#506. |
@doughsay please try to remove the cache from your github actions that your repo is using. It helped in our case. In the repo go to Actions -> Management -> Caches and remove the caches that your PR/branch is using and run the job again. |
Confirmed that deleting the cache resolved the issue on 1.16 without needing to pin to 1.15. |
It seems this is not an action issue (since we don't control local caches) - and you can use the action's lower level version as part of the cache restore key - so I'll close this for now. Feel free to re-open, or comment, to continue the discussion. On another note, I'll probably look into how to automate (or provide tools for...) in the context of the action itself. |
@starbelly, @ericmj, do you think e.g. the action should output its own version so it could be used as part of the cache restore key? I know we've been around this subject in the past, but don't know if you have better ideas on how to "attack" this problem. Thanks. |
Yeah I have the same issue
|
@apoorv-2204, did you try clearing the cache? This new action version introduced new elements in the filesystem that might cause issues with the currently cached elements. |
Our CI started failing after the new 1.16.0 release with this error when running dialyzer:
Here are some details from the action:
Set up Job
The text was updated successfully, but these errors were encountered: