Re: Old PLT file?

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 i=
s complaining =E2=80=9Cold=E2=80=9D.

And since this involves CI within GitHub, you might check how you =E2=80=9Cc=
ache=E2=80=9D the PLT file as well.

I have no documentation at hand, might it be documented somewhere?
(dialyzer related I guess)

Yao

> =E5=9C=A8 2022=E5=B9=B43=E6=9C=8830=E6=97=A5=EF=BC=8C04:20=EF=BC=8CMichael=
 L Martin <[email protected]> =E5=86=99=E9=81=93=EF=BC=9A
>=20
> =EF=BB=BFHi everyone,
>=20
> We are doing our CI on github. We cache the PLT so that we don't have to r=
ebuild it every time, and this mostly works fine, but occasionally dialyzer (=
or, rather, "mix dialyzer", as this is an Elixir/Phoenix application) determ=
ines that the PLT is old and the workflow is aborted.
>=20
> My question is, what makes a PLT file "old"? We very seldom change version=
s 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 cou=
ld understand a little better about what makes a PLT old, perhaps I could so=
lve this issue.
>=20
> Thanks,
>=20
> Michael Martin