Might make most sense as part of a cron job rather than on every PR.
-- Marten
On Wed, Sep 5, 2018 at 8:59 PM Ralf Gommers wrote:
>
>
> On Wed, Sep 5, 2018 at 3:15 PM Tyler Reddy
> wrote:
>
>> Hi,
>>
>> Stefan & Matti wanted me to check on the mailing list about about adding
>> ARMv8 (free /
On Wed, Sep 5, 2018 at 3:15 PM Tyler Reddy wrote:
> Hi,
>
> Stefan & Matti wanted me to check on the mailing list about about adding
> ARMv8 (free / shippable service) to NumPy CI on github -- is anyone opposed
> to that?
>
sounds fine (and useful) to me.
>
> Only obvious drawback seems to be
On Wed, Sep 5, 2018 at 5:38 PM David Grote wrote:
>
> Hi - I have recently come across this problem. On my mac, I build a
> Fortran code, producing a shared object, that I import into Python along
> with numpy. This had been working fine until recently when I started seeing
> sag faults deep
Hi - I have recently come across this problem. On my mac, I build a Fortran
code, producing a shared object, that I import into Python along with
numpy. This had been working fine until recently when I started seeing sag
faults deep inside the Fortran code, usually in Fortran print statements. I
Hi,
Stefan & Matti wanted me to check on the mailing list about about adding
ARMv8 (free / shippable service) to NumPy CI on github -- is anyone opposed
to that?
Only obvious drawback seems to be that the service sometimes seems a little
unreliable, not that this is new to us; guess we could
