Old PLT file?

[Frank Muller]

Glad you find a solution. Would be great if you can share the config
mistake here so others could avoid it.


Thanks for the input. The problem turned out to be a subtle bug in my CI
> script. Probably a cut-n-paste thing. All is now well.
>
>
> On 3/29/22 21:15, Yao Bao wrote:
> > Hello,
> >
> > More detailed information/logging message might be helpful to determine
> this.
> >
> > Since PLT comes from Erlang, and you are using Elixir, you should check
> who is complaining “old”.
> >
> > And since this involves CI within GitHub, you might check how you
> “cache” the PLT file as well.
> >
> > I have no documentation at hand, might it be documented somewhere?
> > (dialyzer related I guess)
> >
> > Yao
> >
> >> 在 2022年3月30日，04:20，Michael L Martin <mmartin4242@REDACTED> 写道：
> >>
> >> Hi everyone,
> >>
> >> We are doing our CI on github. We cache the PLT so that we don't have
> to rebuild it every time, and this mostly works fine, but occasionally
> dialyzer (or, rather, "mix dialyzer", as this is an Elixir/Phoenix
> application) determines that the PLT is old and the workflow is aborted.
> >>
> >> My question is, what makes a PLT file "old"? We very seldom change
> versions of OTP or Elixir, nor do our dependency versions change very
> often, yet we get into this situation a lot more often than I believe we
> should. If I could understand a little better about what makes a PLT old,
> perhaps I could solve this issue.
> >>
> >> Thanks,
> >>
> >> Michael Martin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20220330/bbdd8df1/attachment.htm>