Re: Sage 4.1.1.alpha0 released
Minh Nguyen
> Hi folks,
>
> This is the first release of the Sage 4.1.1 release cycle. William and
> I are co-chairing this release cycle. The source tarball and the
> sage.math only binary are available at
>
> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0.tar
> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0-sage.math.washington.edu-x86_64-Linux.tar.gz
>
> You can also upgrade using this path:
>
> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0/
Upgrade OK on 32-bit Ubuntu 9.04 with Pentium(R) 4 CPU 3.00GHz. The
following tests failed:
sage -t -long devel/sage-main/sage/interfaces/sage0.py # 27 doctests failed
sage -t -long devel/sage-main/sage/interfaces/r.py # 1 doctests failed
sage -t -long devel/sage-main/sage/interfaces/ecm.py # 0 doctests failed
sage -t -long devel/sage-main/sage/groups/perm_gps/partn_ref/refinement_matrices.pyx
# 0 doctests failed
sage -t -long devel/sage-main/sage/schemes/elliptic_curves/ell_rational_field.py
# 0 doctests failed
sage -t -long devel/sage-main/sage/misc/randstate.pyx # 2 doctests failed
Notice the ones with "0 doctests failed". Full log is up at
http://sage.math.washington.edu/home/mvngu/patch/doctest-sage-4.1.1.alpha0.log.bz2
--
Regards
Minh Van Nguyen
Alex Ghitza
>
> On Tue, Jul 21, 2009 at 1:04 PM, Minh Nguyen<nguye...@gmail.com> wrote:
>> Hi folks,
>>
>> This is the first release of the Sage 4.1.1 release cycle. William and
>> I are co-chairing this release cycle. The source tarball and the
>> sage.math only binary are available at
>>
>> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0.tar
>> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0-sage.math.washington.edu-x86_64-Linux.tar.gz
>>
>> You can also upgrade using this path:
>>
>> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0/
>
Upgraded from 4.1 and passed make ptestlong on a 32-bit archlinux machine.
--
Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne
-- Australia -- http://www.ms.unimelb.edu.au/~aghitza/
davidloeffler
schemes/elliptic_curves/ell_rational_field.py and sage/databases/
jones.py. Presumably these are coming from the tickets
#6045: Robert Bradshaw: Computation of Heegner points [Reviewed by
John Cremona, Minh Van Nguyen]
#6332: Francis Clarke: optional doctest failure -- jones number field
database tests fail [Reviewed by Alex Ghitza]
This is now #6577.
David
On Jul 21, 9:28 am, Alex Ghitza <aghi...@gmail.com> wrote:
> On Tue, Jul 21, 2009 at 5:55 PM, Minh Nguyen<nguyenmi...@gmail.com> wrote:
> > On Tue, Jul 21, 2009 at 1:04 PM, Minh Nguyen<nguyenmi...@gmail.com> wrote:
> >> Hi folks,
>
> >> This is the first release of the Sage 4.1.1 release cycle. William and
> >> I are co-chairing this release cycle. The source tarball and the
> >> sage.math only binary are available at
>
> >>http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0.tar
Dr. David Kirkby
> Hi folks,
>
> This is the first release of the Sage 4.1.1 release cycle. William and
> I are co-chairing this release cycle. The source tarball and the
> sage.math only binary are available at
>
> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0.tar
>
> You can also upgrade using this path:
>
> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0/
>
> work of Alex Ghitza and David Loeffler.
>
> This alpha 0 release includes 5 tickets relating to new SPKG's:
>
> #6380 [ntl-5.4.2.p9.spkg]
> #6443 [zn_poly-0.9.p1.spkg]
> #6445 [pari-2.3.3.p1.spkg]
> #6451 [flint-1.3.0.p2.spkg]
> #6493 [numpy-1.3.0.p1.spkg]
>
> All of these tickets, except for #6493, deal with building the
> corresponding SPKG's on Solaris on the machine t2. This Solaris build
> support is due to the remarkable work of David Kirkby. If you want to
> help out with building SPKG's on Solaris/t2, the following tickets
> need review:
>
> #6453
> #6558
#6558 "Be more selective in patching ATLAS on Solaris"
http://sagetrac.org/sage_trac/ticket/6558
should be very easy to review, as the change is very small.
#6453 "MPFR test failures on Solaris 10 update 4 on host 't2'"
http://sagetrac.org/sage_trac/ticket/6453
Is somewhat more complex to review. It basically applies a very simple
patch, in a flexible way - whether the patch is applied or not depends
on the type of Solaris machine and if the user has set an environment
variable to over-ride the default behavior.
Ticket #6563 "Singular fails to install header files, since it fails to
find install-sh"
http://sagetrac.org/sage_trac/ticket/6563
Is an easy one to review, but perhaps a bit controversial. It applies a
quick fix (add a copy of install-sh) to the 15 or so copies of the same
name in the singular distribution. It however add that copy in the top
level directory (where spkg-install exists). It can not possibly break
anything else, and it allows singular to build.
There are undoubtedly other ways to get around this problem, but none
are quite as simple. The real solution is to fix a bug in autoconf or
fix the singular build systems - whatever one happens to be at fault.
I'm personally a bit reluctant to spend much time on finding a better
solution, when there are other parts of Sage which have more serious
problems on Solaris.
Dave
davidloeffler
On Jul 21, 10:56 am, davidloeffler <dave.loeff...@gmail.com> wrote:
> I'm seeing some errors building the reference manual, from sage/
> schemes/elliptic_curves/ell_rational_field.py and sage/databases/
> jones.py. Presumably these are coming from the tickets
>
> #6045: Robert Bradshaw: Computation of Heegner points [Reviewed by
> John Cremona, Minh Van Nguyen]
> #6332: Francis Clarke: optional doctest failure -- jones number field
> database tests fail [Reviewed by Alex Ghitza]
>
> This is now #6577.
easy one for someone to review.
David
John H Palmieri
> Hi folks,
>
> This is the first release of the Sage 4.1.1 release cycle. William and
> I are co-chairing this release cycle. The source tarball and the
> sage.math only binary are available at
>
> You can also upgrade using this path:
>
> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0/
An upgrade failed, but a build from scratch worked. Two failures:
sage -t -long "devel/sage/sage/interfaces/r.py"
sage -t -long "devel/sage/sage/symbolic/expression.pyx"
although the first of these is not repeatable. When it failed, it
said
sage -t -long "devel/sage/sage/interfaces/r.py"
**********************************************************************
File "/Applications/sage_builds/sage-4.1.1.alpha0/devel/sage/sage/
interfaces/r.py", line 838:
sage: r.completions('tes')
Expected:
['testPlatformEquivalence', 'testVirtual']
Got:
<BLANKLINE>
Building R command completion list (this takes
a few seconds only the first time you do it).
To force rebuild later, delete /Users/palmieri/.sage//
r_commandlist.sobj.
['testPlatformEquivalence', 'testVirtual']
**********************************************************************
The second failure is repeatable:
sage -t -long "devel/sage/sage/symbolic/expression.pyx"
**********************************************************************
File "/Applications/sage_builds/sage-4.1.1.alpha0/devel/sage/sage/
symbolic/expression.pyx", line 2503:
sage: ((x+y)^a).match(w0^w1)
Expected:
{$1: a, $0: x + y}
Got:
{$0: x + y, $1: a}
**********************************************************************
File "/Applications/sage_builds/sage-4.1.1.alpha0/devel/sage/sage/
symbolic/expression.pyx", line 2509:
sage: ((a+b)*(a+c)).match((a+w0)*(a+w1))
Expected:
{$1: c, $0: b}
Got:
{$0: b, $1: c}
**********************************************************************
File "/Applications/sage_builds/sage-4.1.1.alpha0/devel/sage/sage/
symbolic/expression.pyx", line 2515:
sage: (a*(x+y)+a*z+b).match(a*w0+w1)
Expected:
{$1: a*z + b, $0: x + y}
Got:
{$0: x + y, $1: a*z + b}
**********************************************************************
Rob Beezer
> What happens if you do an upgrade instead of compiling everything from source?
As an upgrade it built fine and testing gave:
The following tests failed:
sage -t devel/sage/sage/interfaces/r.py # 1 doctests failed
sage -t devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py
# 0 doctests failed
sage -t devel/sage/sage/graphs/graph.py # 0 doctests failed
These all passed when run individually.
I'm trying another build from source right now.
> The log is too big. Compressed logs can be downloaded quicker.
Ooops.
Robert Miller
probably has something to do with MANIFEST.in not pointing out the
following files:
[rlm-book sage-main]$ hg status
! sage/server/notebook/templates/async_lib.js
! sage/server/notebook/templates/jmol_lib.js
! sage/server/notebook/templates/notebook_lib.js
gsw
On 21 Jul., 17:14, John H Palmieri <jhpalmier...@gmail.com> wrote:
> On Jul 20, 8:04 pm, Minh Nguyen <nguyenmi...@gmail.com> wrote:
>
> > Hi folks,
>
> > This is the first release of the Sage 4.1.1 release cycle. William and
> > I are co-chairing this release cycle. The source tarball and the
> > sage.math only binary are available at
>
> > You can also upgrade using this path:
>
> >http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0/
>
> Intel Mac, OS X 10.5:
>
> An upgrade failed, but a build from scratch worked. Two failures:
>
> sage -t -long "devel/sage/sage/interfaces/r.py"
> sage -t -long "devel/sage/sage/symbolic/expression.pyx"
>
> although the first of these is not repeatable. When it failed, it
> said
>
> sage -t -long "devel/sage/sage/interfaces/r.py"
> **********************************************************************
> File "/Applications/sage_builds/sage-4.1.1.alpha0/devel/sage/sage/
> interfaces/r.py", line 838:
> sage: r.completions('tes')
> Expected:
> ['testPlatformEquivalence', 'testVirtual']
> Got:
> <BLANKLINE>
> Building R command completion list (this takes
> a few seconds only the first time you do it).
> To force rebuild later, delete /Users/palmieri/.sage//
> r_commandlist.sobj.
> ['testPlatformEquivalence', 'testVirtual']
> **********************************************************************
>
It seems I somehow managed to mess up my "R" patch at #6379, since the
file
/Users/palmieri/.sage//r_commandlist.sobj
should not be built by running the doctests, nor should the doctests
rely on its existence when they are run a second, third, .., time.
Sorry for that, I'll have a look into this.
Cheers,
Georg
gsw
> > sage -t -long "devel/sage/sage/interfaces/r.py"
> > **********************************************************************
> > File "/Applications/sage_builds/sage-4.1.1.alpha0/devel/sage/sage/
> > interfaces/r.py", line 838:
> > sage: r.completions('tes')
> > Expected:
> > ['testPlatformEquivalence', 'testVirtual']
> > Got:
> > <BLANKLINE>
> > Building R command completion list (this takes
> > a few seconds only the first time you do it).
> > To force rebuild later, delete /Users/palmieri/.sage//
> > r_commandlist.sobj.
> > ['testPlatformEquivalence', 'testVirtual']
> > **********************************************************************
>
> Oh dear.
> It seems I somehow managed to mess up my "R" patch at #6379, since the
> file
> /Users/palmieri/.sage//r_commandlist.sobj
> should not be built by running the doctests, nor should the doctests
> rely on its existence when they are run a second, third, .., time.
> Sorry for that, I'll have a look into this.
>
right now. So opening a ticket, uploading a patch, etc. will have to
wait till tomorrow.
> Cheers,
> Georg
Robert Miller
here in about ten minutes:
http://sage.math.washington.edu/home/rlmill/sage-4.1.1.alpha0-i386-Darwin.dmg
Rob Beezer
> > I get the following error building from source on 64-bit Ubuntu 9.04
> > on Intel Core Duo
> >
> > error: could not create 'build/temp.linux-x86_64-2.6': File
> > exists
> > sage: There was an error installing modified sage library code.
On a fresh attempt to build from source, everything went fine. For
the first attempt, the only difference I can discern is that I had set
declare -x MAKE="make -j4"
which in the past has smoothly allowed the build to use both
processors. Is this the cause of my failure? Is this not advisable?
Rob
William Stein
> Is this not advisable?
It is advisable. You should do that. I do it all the time.
>
> Rob
> >
>
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
Craig Citro
>> the first attempt, the only difference I can discern is that I had set
>>
>> declare -x MAKE="make -j4"
>>
>> which in the past has smoothly allowed the build to use both
>> processors. Is this the cause of my failure?
>
> No idea....
>
This is a known race condition -- for a patch, see
http://trac.sagemath.org/sage_trac/ticket/6374
The patch *should* fix the issue, but since it's an intermittent
problem, it's hard to know that it's *completely* fixed. This was
merged during 4.0.2, but somehow we mixed up merge trees and it wasn't
in the final release. I asked to get it into the last release, but it
still didn't make it ... maybe it'll make it in again soon? I marked
the ticket "needs review," but as I say on the ticket, it's actually
been reviewed once. It felt like cheating to make a new ticket and
list it as "with positive review." :)
-cc
Rob Beezer
Thanks for the explanation - that's consistent with what I saw.
I'll make a mental note to help ensure this gets into the next
release.
Rob
John Cremona
64-bit linux:
sage -t "devel/sage/sage/interfaces/r.py"
32-bit linux:
sage -t "devel/sage/sage/interfaces/r.py"
File "./r.py", line 18
from devel/sage/sage/interfaces/r import *
^
SyntaxError: invalid syntax
and
sage -t "devel/sage/sage/graphs/graph_plot.py"
File "./graph_plot.py", line 18
from devel/sage/sage/graphs/graph_plot import *
^
SyntaxError: invalid syntax
If it is reelvant, the second machine has R installed while the first does not.
2009/7/22 Rob Beezer <goo...@beezer.cotse.net>:
Minh Nguyen
> Hi folks,
>
> This is the first release of the Sage 4.1.1 release cycle. William and
> I are co-chairing this release cycle. The source tarball and the
> sage.math only binary are available at
>
> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0-sage.math.washington.edu-x86_64-Linux.tar.gz
>
> You can also upgrade using this path:
>
> http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0/
Upgraded OK on 32-bit Debian Lenny, Core 2 Duo. The following tests failed:
sage -t -long devel/sage-main/sage/modules/vector_real_double_dense.pyx
**********************************************************************
File "/home/mvngu/usr/bin/sage/devel/sage-main/sage/modules/vector_real_double_dense.pyx",
line 72:
sage: v.stats_skew()
Expected:
0.0
Got:
doctest:106: SyntaxWarning: assertion is always true, perhaps
remove parentheses?
0.0
**********************************************************************
1 items had failures:
1 of 4 in __main__.example_2
***Test Failed*** 1 failures.
For whitespace errors, see the file
/home/mvngu/usr/bin/sage/tmp/.doctest_vector_real_double_dense.py
[3.1 s]
<SNIP>
sage -t -long devel/sage-main/sage/interfaces/r.py
**********************************************************************
File "/home/mvngu/usr/bin/sage/devel/sage-main/sage/interfaces/r.py", line 838:
sage: r.completions('tes')
Expected:
['testPlatformEquivalence', 'testVirtual']
Got:
<BLANKLINE>
Building R command completion list (this takes
a few seconds only the first time you do it).
To force rebuild later, delete /home/mvngu/.sage//r_commandlist.sobj.
['testPlatformEquivalence', 'testVirtual']
**********************************************************************
1 items had failures:
1 of 3 in __main__.example_34
***Test Failed*** 1 failures.
For whitespace errors, see the file /home/mvngu/usr/bin/sage/tmp/.doctest_r.py
[10.5 s]
Jaap Spies
> Fresh builds of 4.1.1.alpha0:
>
> 64-bit linux:
> The following tests failed:
> sage -t "devel/sage/sage/interfaces/r.py"
>
Same here on Fedora 10 and Fedora 11, 32 bit.
In addition both in a fresh install and in an upgrade:
sage -t "devel/sage/sage/combinat/words/morphism.py"
**********************************************************************
File "/home/jaap/Download/sage-4.1/devel/sage/sage/combinat/words/morphism.py", line 616:
sage: m.extend_by(n)
Expected:
Morphism from Words over Ordered Alphabet ['a', 'b', 0, 1] to Words over Ordered Alphabet ['a', 'b', 0, 1]
Got:
Morphism from Words over Ordered Alphabet [0, 1, 'a', 'b'] to Words over Ordered Alphabet [0, 1, 'a', 'b']
**********************************************************************
File "/home/jaap/Download/sage-4.1/devel/sage/sage/combinat/words/morphism.py", line 618:
sage: n.extend_by(m)
Expected:
Morphism from Words over Ordered Alphabet ['a', 'b', 0, 1] to Words over Ordered Alphabet ['a', 'b', 0, 1, 5]
Got:
Morphism from Words over Ordered Alphabet [0, 1, 'a', 'b'] to Words over Ordered Alphabet [0, 1, 5, 'a', 'b']
**********************************************************************
1 items had failures:
2 of 10 in __main__.example_11
***Test Failed*** 2 failures.
For whitespace errors, see the file /home/jaap/Download/sage-4.1/tmp/.doctest_morphism.py
[3.2 s]
exit code: 1024
Jaap
Minh Nguyen
I see the same thing on a freshly compiled Sage 4.1.1.alpha0, but not
in my merge tree.
slabbe
This is now http://trac.sagemath.org/sage_trac/ticket/6593.
I will post a patch soon.
Seb
Minh Nguyen
On Wed, Jul 22, 2009 at 5:39 AM, Robert Miller<rlmil...@gmail.com> wrote:
>
This has been traced to ticket #6307. I'm reverting that ticket,
reopened it, and have marked it as "needs work".
Jaap Spies
> Bonjour Jaap,
>
> This is now http://trac.sagemath.org/sage_trac/ticket/6593.
>
> I will post a patch soon.
>
Thanks! I could not apply the patch{
sage: hg_sage.patch('../trac_6593-word-morphism-doctest-sl.patch')
cd "/home/jaap/downloads/sage-4.1.1.alpha0/devel/sage" && hg status
/home/jaap/downloads/sage-4.1.1.alpha0/local/lib/python2.6/site-packages/sage/misc/hg.py:240: DeprecationWarning: os.popen3 is deprecated. Use the subprocess
module.
x = os.popen3(s)
cd "/home/jaap/downloads/sage-4.1.1.alpha0/devel/sage" && hg status
cd "/home/jaap/downloads/sage-4.1.1.alpha0/devel/sage" && hg import "/home/jaap/downloads/trac_6593-word-morphism-doctest-sl.patch"
abort: outstanding uncommitted changes
sage: hg_sage.status()
Getting status of modified or unknown files:
cd "/home/jaap/downloads/sage-4.1.1.alpha0/devel/sage" && hg status
! sage/server/notebook/templates/async_lib.js
! sage/server/notebook/templates/jmol_lib.js
! sage/server/notebook/templates/notebook_lib.js
---
Jaap
Minh Nguyen
You can't commit anything in Sage 4.1.1.alpha0 since the repository
has been corrupted by the previous patches on ticket #6307. One option
is to refer to the new patches on #6307 for a fix. Another is to wait
for Sage 4.1.1.alpha1 to get out in a couple of hours. Sage
4.1.1.alpha1 will revert #6307, so that should fix the repository
corruption problem. A third option is to manually revert the patches
on #6307 yourself.
Jaap Spies
Thanks! I reverted --all
Now the patch applied and:
[jaap@paix sage-4.1.1.alpha0]$ ./sage -t "devel/sage/sage/combinat/words/morphism.py"
sage -t "devel/sage/sage/combinat/words/morphism.py"
[4.9 s]
----------------------------------------------------------------------
All tests passed!
Total time for all tests: 4.9 seconds
So I'll give #6593 a positive review.
Jaap
John H Palmieri
> Hi Jaap,
>
>
>
>
>
> On Thu, Jul 23, 2009 at 6:55 AM, Jaap Spies<j.sp...@hccnet.nl> wrote:
>
> > slabbe wrote:
> >> Bonjour Jaap,
>
> >> I will post a patch soon.
>
> > Thanks! I could not apply the patch{
>
> > sage: hg_sage.patch('../trac_6593-word-morphism-doctest-sl.patch')
> > cd "/home/jaap/downloads/sage-4.1.1.alpha0/devel/sage" && hg status
> > x = os.popen3(s)
> > cd "/home/jaap/downloads/sage-4.1.1.alpha0/devel/sage" && hg status
> > cd "/home/jaap/downloads/sage-4.1.1.alpha0/devel/sage" && hg import "/home/jaap/downloads/trac_6593-word-morphism-doctest-sl.patch"
> > abort: outstanding uncommitted changes
>
> > sage: hg_sage.status()
> > Getting status of modified or unknown files:
> > cd "/home/jaap/downloads/sage-4.1.1.alpha0/devel/sage" && hg status
> > ! sage/server/notebook/templates/async_lib.js
> > ! sage/server/notebook/templates/jmol_lib.js
> > ! sage/server/notebook/templates/notebook_lib.js
>
> You can't commit anything in Sage 4.1.1.alpha0 since the repository
> has been corrupted by the previous patches on ticket #6307. One option
> is to refer to the new patches on #6307 for a fix. Another is to wait
> for Sage 4.1.1.alpha1 to get out in a couple of hours. Sage
> 4.1.1.alpha1 will revert #6307, so that should fix the repository
> corruption problem. A third option is to manually revert the patches
> on #6307 yourself.
apply patches. Am I hallucinating again?
John
Minh Nguyen
On Thu, Jul 23, 2009 at 7:54 AM, John H Palmieri<jhpalm...@gmail.com> wrote:
<SNIP>
>> You can't commit anything in Sage 4.1.1.alpha0 since the repository
>> has been corrupted by the previous patches on ticket #6307. One option
>> is to refer to the new patches on #6307 for a fix. Another is to wait
>> for Sage 4.1.1.alpha1 to get out in a couple of hours. Sage
>> 4.1.1.alpha1 will revert #6307, so that should fix the repository
>> corruption problem. A third option is to manually revert the patches
>> on #6307 yourself.
>
> It seems to me that in 4.1.1.alpha0, if I make a clone, then I can
> apply patches. Am I hallucinating again?
No, not really. If you're using the binary version of Sage
4.1.1.alpha0, then you can commit and there's no repo corruption and
hg doesn't complain about missing .js files. But if you're using the
source distribution of Sage 4.1.1.alpha0, then hg complains about
missing .js files. If you're using the source distribution and you've
cloned the main repository of that distribution, then I have no ideas
since I just deleted my source distribution of Sage 4.1.1.alpha0
before you asked the question. (Mental note to self: compile the
source distribution of each release and don't delete it until the next
release :-)
Minh Nguyen
On Fri, Jul 24, 2009 at 4:02 AM, Kiran Kedlaya<ksk...@gmail.com> wrote:
>
> Running make ptestlong (which I had never tried before on this
> machine), I see the following failures on 64-bit (Opteron) Fedora 10.
>
> sage -t -long devel/sage/sage/interfaces/r.py # 1 doctests
> failed
> sage -t -long devel/sage/sage/schemes/elliptic_curves/
> ell_rational_field.py # 0 doctests failed
> sage -t -long devel/sage/sage/schemes/elliptic_curves/
> sha_tate.py # 0 doctests failed
> sage -t -long devel/sage/sage/groups/perm_gps/partn_ref/
> refinement_matrices.pyx # 0 doctests failed
>
> The three "0 doctests failed" are timeouts; they pass when run
> individually. The R failure gave
> **********************************************************************
> File "/scratch/sage-4.1.1.alpha0/devel/sage-main/sage/interfaces/
> r.py", line 838:
> sage: r.completions('tes')
> Expected:
> ['testPlatformEquivalence', 'testVirtual']
> Got:
> <BLANKLINE>
> Building R command completion list (this takes
> a few seconds only the first time you do it).
> To force rebuild later, delete /home/r1/kedlaya/.sage//
> r_commandlist.sobj.
> ['testPlatformEquivalence', 'testVirtual']
> **********************************************************************
> but passes if I run it again. However, if I then delete the file
> ~/.sage/r_commandlist.sobj, the failure reappears.
This has been fixed by ticket #6594
http://trac.sagemath.org/sage_trac/ticket/6594