Building on my own Sun Blade 1000, then running
'make ptestlong', I get:
The following tests failed:
sage -t -long devel/sage/sage/graphs/generic_graph.py # 1 doctests
failed
sage -t -long devel/sage/sage/schemes/elliptic_curves/BSD.py # 1
doctests failed
sage -t -long devel/sage/sage/sets/set.py # 1 doctests failed
----------------------------------------------------------------------
Total time for all tests: 24001.4 seconds
drkir...@redstart:~/sage-4.4.3.alpha0$
How do these compare with what people are getting on Linux?
Is there anything that can be done about that timeout of test #2, when it gives
up on one algoritm and switches to another on slow machines?
Dave
1)
sage -t -long devel/sage/sage/server/notebook/conf.py (skipping) --
nodoctest.py file in directory
/Failed
"1" [label=" ", texlbl="$1$"];
"1/4" [label=" ", texlbl="$\frac{1}{4}$"];
"4/5" [label=" ", texlbl="$\frac{4}{5}$"];
"-4" [label=" ", texlbl="$-4$"];
"2" [label=" ", texlbl="$2$"];
"-2" [label=" ", texlbl="$-2$"];
"-1/2" [label=" ", texlbl="$-\frac{1}{2}$"];
"-1" [label=" ", texlbl="$-1$"];
<BLANKLINE>
"1/2" -> "-2" [label=" ", texlbl="$x \ {\mapsto}\ \frac{1}{x}$"];
"1/2" -> "2/3" [label=" ", texlbl="$x \ {\mapsto}\ \frac{1}{x + 1}$"];
"1" -> "-1" [label=" ", texlbl="$x \ {\mapsto}\ \frac{1}{x}$"];
"1" -> "1/2" [label=" ", texlbl="$x \ {\mapsto}\ \frac{1}{x + 1}$"];
"1/4" -> "-4" [label=" ", texlbl="$x \ {\mapsto}\ \frac{1}{x}$"];
"1/4" -> "4/5" [label=" ", texlbl="$x \ {\mapsto}\ \frac{1}{x + 1}$"];
"2" -> "-1/2" [label=" ", texlbl="$x \ {\mapsto}\ \frac{1}{x}$"];
"2" -> "1/3" [label=" ", texlbl="$x \ {\mapsto}\ \frac{1}{x + 1}$"];
}
**********************************************************************
1 items had failures:
1 of 20 in __main__.example_180
***Test Failed*** 1 failures.
For whitespace errors, see the file
/export/home/drkirkby/.sage//tmp/.doctest_generic_graph.py
[355.5 s]
2)
sage -t -long devel/sage/sage/graphs/base/graph_backends.py
[9.8 s]
/
ord_p(#Sha_an) = 2
Remaining primes:
p = 3: irreducible, surjective, non-split multiplicative
(0 <= ord_p <= 2)
[3]
Got:
p = 2: True by 2-descent
Timeout stopped Heegner index computation...
Proceeding to use heegner_index_bound instead.
True for p not in {2, 3} by Kolyvagin.
p = 3 may divide the Heegner index, for which only a bound was computed.
ALERT: p = 3 left in Kolyvagin bound
0 <= ord_p(#Sha) <= 2
ord_p(#Sha_an) = 2
Remaining primes:
p = 3: irreducible, surjective, non-split multiplicative
(0 <= ord_p <= 2)
[3]
**********************************************************************
1 items had failures:
1 of 35 in __main__.example_6
***Test Failed*** 1 failures.
For whitespace errors, see the file
/export/home/drkirkby/.sage//tmp/.doctest_BSD.py
[133.8 s]
3)
sage -t -long devel/sage/sage/sets/set.py
**********************************************************************
File "/export/home/drkirkby/sage-4.4.3.alpha0/devel/sage-main/sage/sets/set.py",
line 316:
sage: Primes() < Set(QQ)
Expected:
True
Got:
False
**********************************************************************
1 items had failures:
1 of 7 in __main__.example_10
***Test Failed*** 1 failures.
For whitespace errors, see the file
/export/home/drkirkby/.sage//tmp/.doctest_set.py
[11.5 s]
--
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
