I take everything back; I have no idea how I passed "make ptestlong" earlier -- but the failure is still very much here. I think it can be triggered somewhat reliably with
./sage -bt src/sage/combinat/dyck_word.py while at the same time ./sage -t src/sage/combinat/dyck_word.py passes without error. This is really strange. Benjamin Am Samstag, 18. April 2015 00:13:59 UTC+2 schrieb vdelecroix: > > At least I opened #18244... > > On 18/04/15 00:02, Benjamin Hackl wrote: > > Vincent, did you also upgrade to 6.7.beta0 or 6.7.beta1 from a previous > > version? > > > > I just finished building 6.7.beta1 after "make distclean", and this time > I > > can't reproduce the error. > > Unfortunately, this doesn't really explain what happened earlier, and > there > > is still the possibilty that > > the error is random. > > > > I will continue to investigate this by running ptestlong a few more > times; > > if I find something out of the > > ordinary I'll report back here. > > > > Benjamin > > > > Am Freitag, 17. April 2015 21:38:18 UTC+2 schrieb Benjamin Hackl: > >> > >> Strange. I'm also trying to find out what triggers the error, no > success > >> yet. > >> > >> Jan Keitel also encountered this error ( > >> http://trac.sagemath.org/ticket/18237#comment:6) -- and I'm sure > >> that there are others with the same problem. > >> > >> Benjamin > >> > >> Am Freitag, 17. April 2015 21:17:10 UTC+2 schrieb vdelecroix: > >>> > >>> Hello Benjamin, > >>> > >>> Indeed, it was after a "make ptestlong" or something similar. And it > >>> reproduced on both sage-6.7.beta0 and sage-6.7.beta1. > >>> > >>> The error is very strange since it corresponds to a test of some > return > >>> type. I will try to get something more verbose. And there is no > caching > >>> involved as far as I can tell... > >>> > >>> Vincent > >>> > >>> On 17/04/15 19:48, Benjamin Hackl wrote: > >>>> Hi Vincent, > >>>> > >>>> well, at least I'm not the only one. For now, I don't really have a > >>> clue > >>>> regarding where this could come from. > >>>> I'm still compiling a clean version of 6.7.beta1, but now I guess > that > >>>> won't change much. > >>>> > >>>> The circumstance that this error only seems to appear after a series > of > >>>> doctests (I suppose you ran "make > >>>> ptestlong" too?) confuses me. Could this point towards something like > >>>> caching or memory leak? > >>>> > >>>> Benjamin > >>>> > >>>> > >>>> Am Freitag, 17. April 2015 19:19:09 UTC+2 schrieb vdelecroix: > >>>>> > >>>>> Hello, > >>>>> > >>>>> It seems that I am not the only one to have troubles with Dyck > >>> words... > >>>>> > >>>>> sage -t --long --warn-long 81.8 src/sage/combinat/dyck_word.py > >>>>> > ********************************************************************** > >>>>> File "src/sage/combinat/dyck_word.py", line 3501, in > >>>>> sage.combinat.dyck_word.DyckWords_size.__init__ > >>>>> Failed example: > >>>>> TestSuite(DyckWords(4,2)).run() > >>>>> Expected nothing > >>>>> Got: > >>>>> ... > >>>>> tester.assert_(isinstance(card, Integer)) > >>>>> ... > >>>>> ------------------------------------------------------------ > >>>>> The following tests failed: > >>> _test_enumerated_set_iter_cardinality > >>>>> > ********************************************************************** > >>>>> 1 item had failures: > >>>>> > >>>>> It occurs several time on my computer (and at least one on Benjamin > >>>>> Hackl's). See > >>>>> > >>>>> http://trac.sagemath.org/ticket/16352#comment:18 > >>>>> http://trac.sagemath.org/ticket/18237#comment:4 > >>>>> > >>>>> Vincent > >>>>> > >>>> > >>> > >> > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
