On Sat, Sep 18, 2010 at 3:44 PM, Mitesh Patel wrote:
> On 09/18/2010 02:10 PM, Robert Bradshaw wrote:
>> On Sat, Sep 18, 2010 at 6:17 AM, Niles wrote:
>>> but the test only runs on sage.math, so is it only a bug on
>>> sage.math?
>>
>> Well, that was a lot easier than having some kind of system
>
On 09/18/2010 02:10 PM, Robert Bradshaw wrote:
> On Sat, Sep 18, 2010 at 6:17 AM, Niles wrote:
>> but the test only runs on sage.math, so is it only a bug on
>> sage.math?
>
> Well, that was a lot easier than having some kind of system
> calibration in place for all other computers...
We *could*
On Sat, Sep 18, 2010 at 6:17 AM, Niles wrote:
>
>> > Well, that is a different issue. I think that sage/tests/startup.py is
>> > a bad test because it is too unpredictable. Sometimes it works,
>> > sometimes it doesn't, depending for example on the load of the system.
>
> indeed; I've had troubl
> > Well, that is a different issue. I think that sage/tests/startup.py is
> > a bad test because it is too unpredictable. Sometimes it works,
> > sometimes it doesn't, depending for example on the load of the system.
indeed; I've had trouble with this too
> Removing the test rather than fixin
