All mac releases, nightly or full, are created in a new VM. It then
installs all the dependencies, downloads all the source code, and
builds everything. Then it copies the release artifacts and build log
out, and then deletes itself. (This is a long way of saying there's
no chance that ngspice-26 code models are being reused :) )
On Mon, Sep 30, 2019 at 11:15 AM Holger Vogt <email address hidden> wrote:
>
> In between ngspice-26 and ngspice-27 there has been a change in the
> codemodel interface that retains the ngspice-26 code models
> incompatible. Could it have happened that the code models of the new
> KiCad builds were not remade and still were version 26 (therefore the
> 'make clean' for the code models)?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1835296
>
> Title:
> simulating laser_driver on macos nightly causes segfault
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1835296/+subscriptions
All mac releases, nightly or full, are created in a new VM. It then
installs all the dependencies, downloads all the source code, and
builds everything. Then it copies the release artifacts and build log
out, and then deletes itself. (This is a long way of saying there's
no chance that ngspice-26 code models are being reused :) )
On Mon, Sep 30, 2019 at 11:15 AM Holger Vogt <email address hidden> wrote: /bugs.launchpad .net/bugs/ 1835296 /bugs.launchpad .net/kicad/ +bug/1835296/ +subscriptions
>
> In between ngspice-26 and ngspice-27 there has been a change in the
> codemodel interface that retains the ngspice-26 code models
> incompatible. Could it have happened that the code models of the new
> KiCad builds were not remade and still were version 26 (therefore the
> 'make clean' for the code models)?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> simulating laser_driver on macos nightly causes segfault
>
> To manage notifications about this bug go to:
> https:/