On Sat, Apr 18, 2009 at 5:24 PM, mabshoff wrote:
>
>
>
> On Apr 18, 5:20 pm, William Stein wrote:
>> On Sat, Apr 18, 2009 at 5:05 PM, Carl Witty wrote:
>>
>> > On Sat, Apr 18, 2009 at 2:46 PM, William Stein wrote:
>> >> I posted a patch so that
>>
>> >> (1) doctests are ran in the same order a
On Apr 18, 5:24 pm, mabshoff wrote:
> One thing that would be nice to see is that one should be able to
run
> the doctest N times with N something like 100 or even 1,000 for
> example and each time a random seed would be picked. Then if any
> failure occurred the doctesting framework should also
On Apr 18, 5:20 pm, William Stein wrote:
> On Sat, Apr 18, 2009 at 5:05 PM, Carl Witty wrote:
>
> > On Sat, Apr 18, 2009 at 2:46 PM, William Stein wrote:
> >> I posted a patch so that
>
> >> (1) doctests are ran in the same order as the file
> >> (2) doctests can be run in random order
> >> (
On Sat, Apr 18, 2009 at 5:19 PM, Rob Beezer wrote:
>
> On Apr 18, 5:05 pm, Carl Witty wrote:
>> OK, what should happen now? I like the patch (except for the name of
>> the command-line argument); but it can't be applied because it makes
>> doctests fail.
>
> I'd suggest the randomized order sho
On Sat, Apr 18, 2009 at 5:05 PM, Carl Witty wrote:
>
> On Sat, Apr 18, 2009 at 2:46 PM, William Stein wrote:
>> I posted a patch so that
>>
>> (1) doctests are ran in the same order as the file
>> (2) doctests can be run in random order
>> (3) doctests can be run in random order specified by a s
On Apr 18, 5:05 pm, Carl Witty wrote:
> OK, what should happen now? I like the patch (except for the name of
> the command-line argument); but it can't be applied because it makes
> doctests fail.
I'd suggest the randomized order should be made available as soon as
possible. It requires a posi
On Apr 18, 5:05 pm, Carl Witty wrote:
> On Sat, Apr 18, 2009 at 2:46 PM, William Stein wrote:
> > I posted a patch so that
>
> > (1) doctests are ran in the same order as the file
> > (2) doctests can be run in random order
> > (3) doctests can be run in random order specified by a seed
>
> >
On Sat, Apr 18, 2009 at 2:46 PM, William Stein wrote:
> I posted a patch so that
>
> (1) doctests are ran in the same order as the file
> (2) doctests can be run in random order
> (3) doctests can be run in random order specified by a seed
>
> Carl, maybe you can referee it:
>
> http://trac.sage
>>
>> Where's the patch?
>>
>> John
>>
>
> Oops. I've posted it now.
>
> William
>
It's very interesting to run on the full rc3 tree with a fixed random
seed. I think this
reveals *numerous* errors and subtle problems:
./sage -tp 20 -long -rand=1 devel/sage/sage/ > testlong-rand1.log&
This
On Sat, Apr 18, 2009 at 3:27 PM, John H Palmieri wrote:
>
> On Apr 18, 2:46 pm, William Stein wrote:
>> On Sat, Apr 18, 2009 at 2:00 PM, Rob Beezer wrote:
>>
>> > Hi Carl,
>>
>> > Thanks for the explanation - good to know just why this was
>> > happening. I'd noticed the tests being run in a d
On Apr 18, 2:46 pm, William Stein wrote:
> On Sat, Apr 18, 2009 at 2:00 PM, Rob Beezer wrote:
>
> > Hi Carl,
>
> > Thanks for the explanation - good to know just why this was
> > happening. I'd noticed the tests being run in a different order as I
> > tried to debug this, but hadn't dug deep en
On Sat, Apr 18, 2009 at 2:00 PM, Rob Beezer wrote:
>
> Hi Carl,
>
> Thanks for the explanation - good to know just why this was
> happening. I'd noticed the tests being run in a different order as I
> tried to debug this, but hadn't dug deep enough to discover the cause.
>
> In misc/latex.py how
Hi Carl,
Thanks for the explanation - good to know just why this was
happening. I'd noticed the tests being run in a different order as I
tried to debug this, but hadn't dug deep enough to discover the cause.
In misc/latex.py how the latex is created often depends on the value
of the boolean EM
On Tue, Apr 14, 2009 at 11:57 AM, John H Palmieri
wrote:
> I figured out how to fix the problem, although I still don't know why
> adding a docstring should cause it.
>
> To fix it: the docstring for "print_or_typeset" contains the lines
...
Well, I can tell you why adding a docstring will cause
On Apr 16, 10:00 pm, Rob Beezer wrote:
> Hi John,
>
> Thanks for the fix! That behavior was driving me crazy. ;-) I've
> been away for a few days, so I'm sorry I didn't reply to your other
> messages as you diagnosed this.
>
> I'll get back to this soon and I'll keep an eye out for any
> expla
Hi John,
Thanks for the fix! That behavior was driving me crazy. ;-) I've
been away for a few days, so I'm sorry I didn't reply to your other
messages as you diagnosed this.
I'll get back to this soon and I'll keep an eye out for any
explanations, in addition to looking at #5610. I've only w
On Apr 11, 5:57 pm, Rob Beezer wrote:
> I've been adding documentation to sage/misc/latex.py and discovered
> that if I add a trivial docstring (empty, one-line, other variants of
> trivial) to the first function in the file (which is "have_dvipng")
> then a test run on that file really goes ha
On Apr 12, 8:47 am, John H Palmieri wrote:
> On Apr 11, 6:34 pm, Rob Beezer wrote:
>
>
>
>
>
> > On Apr 11, 5:59 pm, William Stein wrote:
>
> > > You could post your file.
>
> > Its at http://buzzard.ups.edu/private/latex.py
>
> > This is the fubared version of sage/misc/latex.py (which I am i
On Apr 11, 6:34 pm, Rob Beezer wrote:
> On Apr 11, 5:59 pm, William Stein wrote:
>
> > You could post your file.
>
> Its at http://buzzard.ups.edu/private/latex.py
>
> This is the fubared version of sage/misc/latex.py (which I am in the
> middle of working on). It contains one doctest that I'v
On Apr 11, 5:59 pm, William Stein wrote:
> You could post your file.
Its at http://buzzard.ups.edu/private/latex.py
This is the fubared version of sage/misc/latex.py (which I am in the
middle of working on). It contains one doctest that I've edited
heavily, so some changes seem to be allowed
On Sat, Apr 11, 2009 at 5:57 PM, Rob Beezer wrote:
>
> I've been adding documentation to sage/misc/latex.py and discovered
> that if I add a trivial docstring (empty, one-line, other variants of
> trivial) to the first function in the file (which is "have_dvipng")
> then a test run on that file
21 matches
Mail list logo
