Re: [sage-release] Sage 8.8.beta4 released

My patchbot atlas only sees the usual remaining failures: sage -t --long src/sage/graphs/generators/families.py # 1 doctest failed sage -t --long src/sage/graphs/generic_graph.py # 8 doctests failed sage -t --long src/sage/graphs/graph_database.py # 1 doctest failed and not the many failures

Re: [sage-release] Sage 8.8.beta3 released

Maybe your computer is *too fast* ? What is the result of manually running the following line: run_doctests(sage.rings.infinity) On my computer, I get with python3 too few successful tests, not using stored timings Running doctests with ID 2019-04-29-10-37-46-21ab2187. Git branch: develop

[sage-release] Re: Sage 8.7.rc0 released

Failure to build "zn_poly" with python3 on one machine, see https://trac.sagemath.org/ticket/27476#comment:8 and discussion that follows Frédéric Le mercredi 20 mars 2019 00:03:34 UTC+1, Volker Braun a écrit : > > As always, you can get the latest beta version from the "develop" git >

Re: [sage-release] Re: Sage 8.7.beta0 released

installing libffi-dev on the system and doing ./configure fixed the problem. Thanks ! Le jeudi 24 janvier 2019 13:45:37 UTC+1, E. Madison Bray a écrit : > > On Thu, Jan 24, 2019 at 9:40 AM > wrote: > > > > I have the same issue with libffi ! > > I will look into that ASAP. It's a similar /

[sage-release] Re: Sage 8.7.beta0 released

This libffi warning/failure does not prevent sage to run and work. It prevents my patchbot to work correctly though. Le jeudi 24 janvier 2019 09:40:52 UTC+1, fchap...@gmail.com a écrit : > > I have the same issue with libffi ! > > Le jeudi 24 janvier 2019 06:08:53 UTC+1, Steven Trogdon a écrit :

[sage-release] Re: Sage 8.7.beta0 released

I have the same issue with libffi ! Le jeudi 24 janvier 2019 06:08:53 UTC+1, Steven Trogdon a écrit : > > Problem building libffi-3.2.1 on gentoo > > cp: cannot overwrite non-directory > '/64bitdev/storage/sage-git_develop/sage/local/./lib64' with directory >

[sage-release] Re: Sage 8.6.rc1 released

This is the second consecutive beta release where the progress towards python3 is going backwards, in the sense that more files have failing doctests. Maybe it will soon be time to ask developers to check everything on python3 ? Maybe having a python3 buildbot would be good ? F Le samedi 12

[sage-release] Re: Sage 8.5.beta6 released

Yes, "make doc" failure on python 3 is an important known problem, not currently investigated by anybody. It's a bit sad to be apparently so close to make it work,and to be stalled after so much work on that. Frederic Le lundi 3 décembre 2018 15:25:38 UTC+1, Eric Gourgoulhon a écrit : > > Le

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

Could be caused by https://trac.sagemath.org/ticket/26702 Le mercredi 28 novembre 2018 09:49:53 UTC+1, François Bissey a écrit : > > That’s interesting. I thought the failures in sage/databases/sql_db.py in > sage-on-gentoo > were due to the use of a newer version of sqlite. But if you see it

Re: [sage-release] Re: Sage 8.5.beta3 released

well, my opinion would be to remove the doc building in sagenb spkg-install.. When I comment these lines, everything works fine. Because this tries to import sage.all, this can only work if sage is considered to be fully built.. F Le lundi 12 novembre 2018 11:15:12 UTC+1, Erik Bray a écrit :

[sage-release] Re: Sage 8.5.beta3 released

This seems to break almost all the patchbots. Problem building the sagenb doc, probably. Frederic Le lundi 12 novembre 2018 00:33:09 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

[sage-release] Re: Sage 8.4.beta1 released

This failure was probably caused by the presence of a personal file pip.conf. Trying again now after removing this file. Le jeudi 16 août 2018 08:28:48 UTC+2, fchap...@gmail.com a écrit : > > going from 8.4.b0 to 8.4.b1 fails (on my three machines) with > > [sagelib-8.4.beta1] && sage-python23

[sage-release] Re: Sage 8.4.beta1 released

going from 8.4.b0 to 8.4.b1 fails (on my three machines) with [sagelib-8.4.beta1] && sage-python23 -u setup.py --no-user-cfg build install [sagelib-8.4.beta1] [sagelib-8.4.beta1] Traceback (most recent call last):

[sage-release] Re: Sage 8.2.rc4 released

Hello, can we hope to have 8.2 released and move on to 8.3.beta soon ? I am really worried by the 161 positive-reviewed tickets that have been accumulating, and by the potential rebase work that will be triggered. Frederic Le vendredi 20 avril 2018 22:28:15 UTC+2, Volker Braun a écrit : > >

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

This is way above my understanding of "make" matters. So help from Erik or Jeroen or whoever is knowledgeable in this kind of things, is required. Le vendredi 9 février 2018 21:24:34 UTC+1, Volker Braun a écrit : > > Can you first set up a makefile target that is supposed to be tested? E.g. >

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

Volker, it would be great (and I would appreciate) if you could set up a buildbot that checks that sage builds with python3. One can not yet say that vanilla-sage builds and starts with "export SAGE_PYTHON3=yes", but at least it builds (since some time already). Starting is another matter, but

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

I have a build failure in subprocess32 on a python3 build (using export SAGE_PYTHON3=yes) [subprocess32-3.2.7] Found local metadata for subprocess32-3.2.7 [subprocess32-3.2.7] Attempting to download package subprocess32-3.2.7.tar.gz from mirrors [subprocess32-3.2.7]

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

I sent something at your lri adress. Le vendredi 9 février 2018 13:52:24 UTC+1, Jeroen Demeyer a écrit : > > On 2018-02-09 11:56, fchap...@gmail.com wrote: > > An incremental build from previous beta fails on gfortran : > > Please do > > touch configure.ac && make build > > and send me the

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

I did a make distclean and make. Everything built smoothly. Le vendredi 9 février 2018 12:10:40 UTC+1, François Bissey a écrit : > > Actually if you have the autotools packages installed (from the system or > sage) > can you try > autoreconf -i > then re-run configure and see if that fix it.

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

ubuntu 17.10. There is also at least one patchbot having the same issue, see https://patchbot.sagemath.org/ticket/0/ Le vendredi 9 février 2018 12:02:28 UTC+1, François Bissey a écrit : > > Which version of ubuntu? We have seen an instance of that problem during > review > but we thought it

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

An incremental build from previous beta fails on gfortran : [gfortran-7.2.0] Found local metadata for gfortran-7.2.0 [gfortran-7.2.0] Using cached file /home/chapoton/sage/upstream/gcc-7.2.0.tar.xz [gfortran-7.2.0] gfortran-7.2.0 [gfortran-7.2.0]

[sage-release] Re: Sage 8.1 released

Volker, could you please get rid of the 66 "positive-reviewed as invalid" tickets ? Frédéric https://trac.sagemath.org/query?status=positive_review=sage-duplicate%2Finvalid%2Fwontfix=0=id=summary=owner=type=priority=milestone=component=id Le vendredi 8 décembre 2017 01:06:15 UTC+1, Volker

Re: [sage-release] Re: Sage 8.1.beta3 released

The long-time doctests in function fields should be fixed by the ticket https://trac.sagemath.org/ticket/23683 Hopefully it will be merged soon. Le vendredi 25 août 2017 17:23:55 UTC+2, Erik Bray a écrit : > > On Wed, Aug 23, 2017 at 10:44 AM, Emmanuel Charpentier >

[sage-release] Re: Sage 8.1.beta3 released

This is probably due to the changes in https://trac.sagemath.org/ticket/23193 Le mercredi 23 août 2017 11:55:50 UTC+2, fchap...@gmail.com a écrit : > > function_field doctests are way too long ! > > > sage -t --long --warn-long src/sage/rings/function_field/function_field.py >

[sage-release] Re: Sage 8.1.beta3 released

function_field doctests are way too long ! sage -t --long --warn-long src/sage/rings/function_field/function_field.py ** File "src/sage/rings/function_field/function_field.py", line 67, in sage.

[sage-release] Re: Sage 8.1.beta0 released

Thanks for all your work, Volker. Several patchbots report failures in "sage -t --long src/sage/rings/fraction_field_FpT.pyx # 3 doctests failed". This is apparently a pickling issue. For example, see

[sage-release] Re: Sage 8.0.beta10 released

It seems that this happens on several machines: Error installing package gf2x-1.1.p2 See for example https://patchbot.sagemath.org/log/0/LinuxMint/18.1/x86_64/4.4.0-59-generic/rk02-math/2017-06-11%2018:40:38?short Frederic Le dimanche 11 juin 2017 13:58:04 UTC+2, Volker Braun a écrit : > > As

Re: [sage-release] Re: Sage 8.0.beta8 released

Same for me as for John: after sage -sh math-readline /bin/sh: 1: math: not found the sage shell is not displaying what I am typing. and even the bash shell itself is in the same not-displaying mode. Frederic Le mercredi 31 mai 2017 12:03:08 UTC+2, John Cremona a écrit : > > On 31 May 2017 at

[sage-release] Re: Sage 8.0.beta6 released

for the calculus one (caused by the French locale), see https://trac.sagemath.org/ticket/22833 Le samedi 13 mai 2017 11:55:40 UTC+2, Emmanuel Charpentier a écrit : > > On Debian testig running on core i7 + 16 Gb RAM, ptestlong passes with two > failures : > >

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

Trying to build with SAGE_PYTHON3=yes now fails much earlier than where it should: [sagelib-7.6.beta6] Traceback (most recent call last): [sagelib-7.6.beta6] File "setup.py", line 54, in [sagelib-7.6.beta6] import sage.env [sagelib-7.6.beta6] File "/home/chapoton/sage3/src/sage/env.py",

[sage-release] Re: Sage 7.5.rc3 released

It seems to me that the tag 7.5.rc3 is missing somewhere, and this perturbs the behaviour of patchbots. Frederic Le dimanche 8 janvier 2017 15:32:24 UTC+1, Volker Braun a écrit : > > True, seems like there is a problem in pushing versions to github. I think > its a git hook on

[sage-release] Re: Sage 7.5.beta6 released

culprit ticket is https://trac.sagemath.org/ticket/21613#comment:63 Le samedi 10 décembre 2016 11:50:57 UTC+1, fchap...@gmail.com a écrit : > > I mean that "export SAGE_PYTHON3=yes & make build" breaks at the point > displayed in my message, and it was not doing that before 7.5.b6. > > I monitor

[sage-release] Re: Sage 7.5.beta6 released

I mean that "export SAGE_PYTHON3=yes & make build" breaks at the point displayed in my message, and it was not doing that before 7.5.b6. I monitor on every new release where is the first py3 problem. This is a regression. Frederic Le samedi 10 décembre 2016 11:43:33 UTC+1, Dima Pasechnik a

[sage-release] Re: Sage 7.5.beta6 released

Hello it seems that once again somebody broke the python3 compatibility of the scripts: [sagelib-7.5.beta6] File "/home/chapoton/sage3/src/sage_setup/autogen/__init__.py", line 9, in autogen_all [sagelib-7.5.beta6] pari.rebuild() [sagelib-7.5.beta6] File

Re: [sage-release] Re: cannot build 7.5.b3 (twice)

Le samedi 19 novembre 2016 09:36:06 UTC+1, Jeroen Demeyer a écrit : > > Le samedi 19 novembre 2016 00:36:58 UTC+1, Volker Braun a écrit : > >> What are the permissions on your src/ directory? > >> > >> > > > > It seems to be 775. I do not think I have changed anything about that > > recently. >

[sage-release] Re: cannot build 7.5.b3 (twice)

Le samedi 19 novembre 2016 00:36:58 UTC+1, Volker Braun a écrit : > What are the permissions on your src/ directory? > > It seems to be 775. I do not think I have changed anything about that recently. laptop:~/sage$ ls -ld src drwxrwxr-x 8 chapoton chapoton 4096 nov. 18 22:14 src

[sage-release] cannot build 7.5.b3 (twice)

I have two machines running ubuntu 16.10, on which I have just failed to build 7.5.b3 ! :( I then did "make distclean" and tried again, and got the same failure: [sagelib-7.5.beta3] rm -f sage/libs/pari/auto_*.pxi [sagelib-7.5.beta3] python -c "from sage_setup.autogen.pari import rebuild;