On Tue, Sep 11, 2018 at 11:34 AM Erik Bray <erik.m.b...@gmail.com> wrote:
>
> On Tue, Sep 11, 2018 at 11:08 AM Erik Bray <erik.m.b...@gmail.com> wrote:
> >
> > On Fri, Sep 7, 2018 at 1:24 AM Volker Braun <vbraun.n...@gmail.com> wrote:
> > >
> > > As always, you can get the latest beta version from the "develop" git 
> > > branch. Alternatively, the self-contained source tarball is at 
> > > http://www.sagemath.org/download-latest.html
> >
> > On Cygwin `make ptestlong` with 4 processes gave me a few random
> > failures.  I have a lot of browser tabs open so I'm getting a lot of
> > spurious
> >
> >      ***   Warning: not enough memory, new PARI stack 8545042432
> >
> > warnings as the cause for most of the random failures.  I really need
> > to figure out how to disable that message for good.
> >
> > But I also got this failure again:
> >
> >     sage -t --long --warn-long 168.0 src/sage/parallel/map_reduce.py
> >     **********************************************************************
> >     File "src/sage/parallel/map_reduce.py", line 281, in
> > sage.parallel.map_reduce
> >     Failed example:
> >         st = pstats.Stats(prof+'0')
> >     Expected nothing
> >     Got:
> >         Exception AssertionError: AssertionError('TripleDictEraser:
> > key match but no weakref match',) in
> > <sage.structure.coerce_dict.TripleDictEraser object at 0x6fffe90ef68>
> > ignored
> >     **********************************************************************
> >     1 item had failures:
> >        1 of  48 in sage.parallel.map_reduce
> >         [300 tests, 1 failure, 68.01 s]
> >
> > Last time I saw this I could never manage to reproduce this, but there
> > it is again in the exact same place before, so it's at least not
> > completely random.
>
> Well, I can reproduce this reliably now by running
>
>     SAGE_NUM_THREADS=2 ./sage -t --long src/sage/parallel/map_reduce.py
>
> without the SAGE_NUM_THREADS=2 it doesn't happen.

I think it might be something similar to this issue:
https://bugs.python.org/issue14548  The exact details aren't clear to
me yet, but if you fork in the middle of a garbage collection cycle
(quite likely in the sage.parallel.map_reduce module which is why this
happens to be appearing there), I suppose you could end up in some
fork-unsafe state.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Reply via email to