Re: [sage-release] Sage 6.10.beta5 released

2015-11-24 Thread Rob Beezer 

On SageMathCloud, built from source, passes long tests ("ptestlong").

@Cremona - none of the elliptic curve tests timed-out this time.

Development Images and Build Logs available at:
https://cloud.sagemath.com/projects/53b77207-8614-4086-a032-432af4b4cdbd/files/sage-dev-images/

On 11/22/2015 12:45 PM, Volker Braun wrote:

As always, you can get the latest beta version from the "develop" git branch.
Alternatively, the self-contained source tarball is at
http://www.sagemath.org/download-latest.html

4ca26b3 Updated Sage version to 6.10.beta5
f04c3c7 Trac #19249: Interface with TdLib
23f93e2 Trac #19600: correct a few typoes
5689f93 Trac #19533: Add a method to find a vector x such that Q(x) = C, where Q
is a quadratic form and C is a constant.
3a586db Trac #19392: Add tetrahedral poset code
7bf2275 Trac #19593: interval-posets in Tamari lattice should be hashable..
9e84001 Trac #19584: Clean up NTL comparisons
a6c6865 Trac #19508: Implementing RijndaelGF
5911b2f Trac #19276: precision problem computing heights on elliptic curves
9cafbb6 Trac #19471: COIN backend: More basis status and tableau data functions
2ec5601 Trac #19582: Upgrade boot_cropped to 1.58.0
41862d0 Trac #19588: typos in "iterator" spelling
e8a2fe9 Trac #19579: Declare NTL types as cppclass
be20067 Trac #19480: Fix permissions of qepcad.help
14f5b40 Trac #19472: GLPK backend: More basis status and tableau data functions
13f0610 Trac #17481: Python does not need dpkg-dev anymore on multiarch debians
9ae39ee Trac #19432: Small fixes to the developer's walkthrough
d5d7b10 Trac #19575: Conversion PARI t_STR -> Python str should not keep quotes
5d5d0c3 Trac #19574: src/sage_setup/find.py :  find_extra_files break doctests
if they are not run from SAGE_ROOT directory
93d275b Trac #19501: Factor() of small integer does not check algorithm-keyword
44fed19 Trac #16637: has_finite_order of EllipticCurvePoint performs useless
computations
3414e18 Trac #19559: method -> algorithm, part 2
a24c10d Trac #19566: Jupyter rich output compatibility
057 Trac #19561: enforce Sage integers in Krawtchouk
f41a40b Trac #19495: Fixes a bug in is_mutation_finite for ClusterSeed
34ce791 Trac #19400: move documentation of asymptotic expansion to 
sage.asymptotic
d2fd8ac Trac #19296: Generating function in FindStat interface
fbabbf1 Trac #19113: LatticePoset: Return type category of product()
0d3caa0 Updated Sage version to 6.10.beta4

--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-release+unsubscr...@googlegroups.com
.
To post to this group, send email to sage-release@googlegroups.com
.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 6.10.beta5 released

2015-11-24 Thread Justin C. Walker 

On Nov 24, 2015, at 13:22 , Volker Braun wrote:

> On Tuesday, November 24, 2015 at 9:42:31 PM UTC+1, Justin C. Walker wrote:
>> 
>> This prompts a couple of questions (out of curiosity): 
>> - I trimmed the "--long --warn-long 108.1" part, but sage replaced them, 
>> albeit with a shorter time (105.2).  How do it know?  And why the 
>> difference? 
>> - Why the "long" flags?  The test ran in ~4 seconds. 
>> 
> 
> The warn-long cutoff is scaled based on the speed of your computer as 
> measured by the last successful test run.
> 
> Tests should be near-instantaneous. Everything that takes second(s) is 
> --long. You might think a second is nothing, but if you have 1000s of files 
> with 100s of doctests then things tend to add up.

Thanks; makes sense.

Justin

--
Justin C. Walker, Curmudgeon at Large
Director
Institute for the Enhancement of the Director's Income
---
Nobody knows the trouble I've been
---



-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 6.10.beta5 released

2015-11-24 Thread Volker Braun 
On Tuesday, November 24, 2015 at 9:42:31 PM UTC+1, Justin C. Walker wrote:
>
> This prompts a couple of questions (out of curiosity): 
>  - I trimmed the "--long --warn-long 108.1" part, but sage replaced them, 
> albeit with a shorter time (105.2).  How do it know?  And why the 
> difference? 
>  - Why the "long" flags?  The test ran in ~4 seconds. 
>

The warn-long cutoff is scaled based on the speed of your computer as 
measured by the last successful test run.

Tests should be near-instantaneous. Everything that takes second(s) is 
--long. You might think a second is nothing, but if you have 1000s of files 
with 100s of doctests then things tend to add up.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.