Re: [sage-release] Re: Sage 7.6.beta2 released

[Jeroen Demeyer]

On 2017-02-04 10:34, Jean-Philippe Labbé wrote:

Before that it was building the doc, and before that installing the
jupyter client.


Logs please... ignore the "python" thing, it's most likely not the 
reason for the failure.


--
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 https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.6.beta2 released

[Volker Braun]

On Saturday, February 4, 2017 at 11:55:00 AM UTC+1, Samuel Lelievre wrote:
>
> Should 'make ptestlong' ignore the content of 'init.sage'?
>

Yes. 

>

-- 
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 https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 7.6.beta2 released

[Simon King]

Hi!

On 2017-02-04, Daniel Krenn  wrote:
>> Should 'make ptestlong' ignore the content of 'init.sage'?
>
> +1, I think (without having thought too much about it...)

+1. IIRC, init.sage is about the user's personal configuration
for interactive sessions, and s/he might want to use, say, implicit
multiplication (such that 4x rather than 4*x becomes valid syntax). But
in any task that is not interactive, which includes doctesting, the
interactor's (i.e., user's) personal configuration should be irrelevant.

Cheers,
Simon

-- 
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 https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.6.beta2 released

[Daniel Krenn]

On 2017-02-04 11:54, Samuel Lelièvre wrote:
> You are right Volker!
> 
> I followed the hint in fidbc's answer at [0]
> 
> [0] https://ask.sagemath.org/question/10060/sage-terminal-colors/
> 
> and I have the following 'init.sage':
> 
> $ cat $HOME/.sage/init.sage 
> %colors Linux

I have this as well in my init.sage.

> Should 'make ptestlong' ignore the content of 'init.sage'?

+1, I think (without having thought too much about it...)

> Should I hide my 'init.sage' before running 'make ptestlong'?

This cannot (and should not) be the solution.

Daniel

-- 
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 https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 7.6.beta2 released

[Samuel Lelièvre]

2017-02-04 11:32 GMT+01:00 Volker Braun:

> I think its likely that you have some local configuration, probably
> ipython,
>
that is being picked up accidentally. The failures all come from switching
> on
>
ascii colors even though they shoudn't be for doctests.
>
In any case I can't reproduce it.
>

You are right Volker!

I followed the hint in fidbc's answer at [0]

[0] https://ask.sagemath.org/question/10060/sage-terminal-colors/

and I have the following 'init.sage':

$ cat $HOME/.sage/init.sage
%colors Linux

Should 'make ptestlong' ignore the content of 'init.sage'?
Should I hide my 'init.sage' before running 'make ptestlong'?
Would it make a difference if I followed Sébastien's answer
at [0] instead of fidbc's answer? I can investigate all that in
the coming week.

-- 
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 https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 7.6.beta2 released

[Jean-Philippe Labbé]

Hi,

I get:


Error building Sage.

The following package(s) may have failed to build (not necessarily 
during this run of 'make all'): 

* package: python 
log file: /sage/logs/pkgs/python.log 
build directory: /sage/local/var/tmp/sage/build/python
=

Before that it was building the doc, and before that installing the jupyter 
client.

I did not run the all the test yet, but sage seems to run without problems 
so far.

-- 
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 https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Re: Sage 7.6.beta2 released

[Emmanuel Charpentier]

Indeed... Sorry for the answering delay (NI...).

--
Emmanuel Charpentier

Le jeudi 2 février 2017 14:45:43 UTC+1, Volker Braun a écrit :
>
> Presumably this one: https://trac.sagemath.org/ticket/15585
>
>
> On Thursday, February 2, 2017 at 1:30:04 PM UTC+1, Emmanuel Charpentier 
> wrote:
>>
>> On Debioan testing (Core17 + 16 GB RAM), passes ptestlong with one 
>> failure (sage -t --long --warn-long 109.4 
>> src/sage/homology/simplicial_complex.py ) which is transient (passes with 
>> no error when run standalone).
>>
>> HTH,
>>
>> --
>> Emmanuel Charpentier
>>
>>
>> Le mercredi 1 février 2017 22:39:03 UTC+1, Volker Braun a écrit :
>>>
>>> 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
>>>
>>> 375d4ee Updated SageMath version to 7.6.beta2
>>> eaaf043 Trac #22188: Document Sage's documentation style, in particular 
>>> use ".. FOO::" rather than ".. foo::"
>>> 715b38b Trac #22262: Three.js: Fix axes label offsets for significant 
>>> aspect ratio adjustments
>>> 7744632 Trac #22270: py3 compatible imports in sage/matrix
>>> a3034da Trac #6: Make minimal Three.js a standard package
>>> 4baf6f1 Trac #22122: Remove deprecated code in geometry
>>> 5e68f39 Trac #22248: typos in the word isomorphism
>>> 16478ab Trac #22246: pep8 cleanup of graph_latex
>>> 42944a7 Trac #22132: Make base ring appear in self representation of 
>>> PointConfiguration
>>> f28c7e3 Trac #22053: Doctest continuation marker / several files
>>> 47689bd Trac #22212: Improve method PowerSeries._pari_()
>>> fadc413 Trac #21117: specialzation for polynomials, schemes, and 
>>> morphisms
>>> 9821ed4 Trac #22266: py3: get rid of cmp() in element_wrapper
>>> 0889e0c Trac #22263: Regular matroid isomorphism problem
>>> c7b3060 Trac #22259: py3 do not call cmp() in code of real_mpfr
>>> 80ac45e Trac #22242: py3 : use richcmp for ring morphisms
>>> 9ad2168 Trac #22240: Use relative imports in sage_setup/autogen/pari
>>> fbe5bcc Trac #22198: Make cypari2 Python2 / Python3 compatible
>>> e3a2999 Trac #19625: Lift faster digraph from alcove path to category of 
>>> highest weight crystals
>>> 5ea3fad Trac #22260: mpir fails to build with sed 4.3+
>>> 44047c5 Trac #22251: Fix lie_polynomial
>>> 3c2ef0a Trac #17527: Echelon form of a matrix is sometimes pickled 
>>> incorrectly
>>> 393f6f5 Trac #22216: Constructing a power series from PARI ignores the 
>>> precision
>>> 78587c8 Trac #22210: Remove obsolete special case in PARI gen.eval()
>>> 360b42c Trac #22207: Fix tutorial_free_modules.py
>>> 42b082c Trac #22205: add more links to PARI documentation
>>> a0e40d6 Trac #22172: faster coercion from Python ints to ℚ(√a)
>>> 3a78b8a Trac #22140: remove "import sage" from sage.rings.asymptotic.*
>>> c1247cb Trac #22137: LatticePoset: Add certificate for 
>>> is_join_semidistributive
>>> a8df4ce Trac #21533: add a method to reach lmfdb webpage of elliptic 
>>> curves over Q
>>> 82bf6ce Trac #20729: doctest runner breaks loading modules from packages 
>>> that use relative imports
>>> 3d9cc08 Trac #22255: py3 : use richcmp for padic ring morphisms
>>> 18b1b83 Trac #22254: Speedup computation of bridges
>>> 3e81b55 Trac #22245: py3: no cmp() in noncommutative ideals
>>> f0d434a Trac #22238: LatticePoset: Is subdirectly irreducible?
>>> e56a4ca Trac #22199: cleanup of two files inside stats/distribution
>>> d6ae2a3 Trac #22092: Remove custom method Group.__contains__()
>>> 21679a8 Trac #21594: Fomin's growth diagrams and Schensted-like 
>>> algorithms
>>> 3ade098 Trac #18920: upgrade Maxima  to version >= 5.39
>>> ac31f23 Updated SageMath version to 7.6.beta1
>>>
>>>

-- 
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 https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.