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

Upgrades fine with clang-5.0.1 on OpenSuSE Linux, clang-6 would not compile giac I opened #25324. On Thu, May 10, 2018 at 8:29 AM Henri Girard wrote: > On ubuntu I recently had a problem because curl didn't install properly I > think with bionic I think it's ok > >

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

Builds fine from scratch with clang-5.0.1. sage -gdb will now abort here however. https://trac.sagemath.org/ticket/25196 On Tuesday, April 17, 2018 at 12:34:24 AM UTC+2, Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the

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

Testing on OpenSuSE fails because of https://trac.sagemath.org/ticket/24920 So, still no working patchbots with that system. On Sun, Apr 1, 2018 at 8:46 AM Ralf Stephan <gtrw...@gmail.com> wrote: > Builds fine with clang-5 on OpenSuSE but not with the new clang-6.0.0 due > to gf

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

Builds fine with clang-5 on OpenSuSE but not with the new clang-6.0.0 due to gfan. I opened https://trac.sagemath.org/ticket/25072 On Sun, Apr 1, 2018 at 6:03 AM Justin C. Walker wrote: > > > On Mar 31, 2018, at 15:39 , Volker Braun wrote: > > > > As

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

Builds fine but crashes when testing combinat/posets/poset_examples.py on OpenSuSE. This is fixed by https://trac.sagemath.org/ticket/21828 which is positively reviewed. Please merge! On Wed, Mar 28, 2018 at 9:57 PM Volker Braun wrote: > As always, you can get the latest

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

It would be good to have a final review on #21828, as OpenSuSE systems still fail doctests and so cannot participate as patchbots. On Tue, 13 Mar 2018, 11:26 Ralf Stephan, <gtrw...@gmail.com> wrote: > This is #24918 that was too late to be merged, apparently. > > On Tue, 13 Mar 2

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

This is #24918 that was too late to be merged, apparently. On Tue, 13 Mar 2018, 11:19 Eric Gourgoulhon, wrote: > On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + > pull develop, parallel (-j16) build OK and make ptestlong failed with one >

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

Builds fine using clang-5.0.1 on OpenSuSE Linux. On Tue, Mar 6, 2018 at 4:08 PM Ralf Stephan <gtrw...@gmail.com> wrote: > The test_jupyter.rst fail is now https://trac.sagemath.org/ticket/24918 > > On Tue, Mar 6, 2018 at 10:46 AM Emmanuel Charpentier < > emanuel.charpen

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

The test_jupyter.rst fail is now https://trac.sagemath.org/ticket/24918 On Tue, Mar 6, 2018 at 10:46 AM Emmanuel Charpentier < emanuel.charpent...@gmail.com> wrote: > FWIW, same result onDeian testing running on Core i5 + 8 GB RAM. > > -- > Emmanuel Charpentier > > Le samedi 3 mars 2018 12:09:52

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

, 2018 at 3:43 PM Ralf Stephan <gtrw...@gmail.com> wrote: > Note that (from patchbot page 0) most patchbots fail on > > sage -t--long src/sage/interacts/test_jupyter.rst > > > On Sat, Mar 3, 2018 at 11:17 PM Justin C. Walker <jus...@mac.com> wrote: > >> >&

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

Note that (from patchbot page 0) most patchbots fail on sage -t--long src/sage/interacts/test_jupyter.rst On Sat, Mar 3, 2018 at 11:17 PM Justin C. Walker wrote: > > > On Mar 2, 2018, at 16:50 , Volker Braun wrote: > > > > As always, you can get the

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

beta6 builds fine from scratch with clang-4 on OpenSuSE, without needing patches. Testing later. On Mon, Feb 19, 2018 at 7:38 AM François Bissey wrote: > > > > On 19/02/2018, at 19:36, Justin C. Walker wrote: > > > >> > >> On Feb 18, 2018, at 12:09 ,

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

Finally it turns out for a major Linux distro build with clang no other flags than CC=clang CXX=clang++ are needed, and the #24696 ticket merged. clang-3.8 will result in a crash in linbox (#24701, #24716) so clang-4 is recommended because there are problems with clang-5 as reported in #24704 and

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

https://stackoverflow.com/questions/19901128/enable-libc-libcxx-by-default-when-using-clang On Mon, Feb 12, 2018 at 9:16 AM François Bissey <frp.bis...@gmail.com> wrote: > > > > On 12/02/2018, at 20:06, Ralf Stephan <gtrw...@gmail.com> wrote: > > > > Finally

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

make ptestlong passes on OpenSuSE 42.3 with clang-4.0.1 on top of #24696 with only the usual failures in R and that one reported in #21828. On Mon, Feb 12, 2018 at 8:06 AM Ralf Stephan <gtrw...@gmail.com> wrote: > Finally here is the recommended set of flags for clang on Linux: >

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

st, On Sun, Feb 11, 2018 at 5:53 PM Ralf Stephan <gtrw...@gmail.com> wrote: > See https://trac.sagemath.org/ticket/24701#comment:5 for the current > state of clang on Linux. > > On Sun, Feb 11, 2018 at 3:39 PM Ralf Stephan <gtrw...@gmail.com> wrote: > >> Anot

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

See https://trac.sagemath.org/ticket/24701#comment:5 for the current state of clang on Linux. On Sun, Feb 11, 2018 at 3:39 PM Ralf Stephan <gtrw...@gmail.com> wrote: > Another bug uncovered. With CXXFLAGS='stdlib=libc++' scipy build fails > with, of all things > gfortran: erro

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

Another bug uncovered. With CXXFLAGS='stdlib=libc++' scipy build fails with, of all things gfortran: error: unrecognized command line option '--stdlib=libc++' Huh? On Sun, Feb 11, 2018 at 11:40 AM Simon King <simon.k...@uni-jena.de> wrote: > Hi! > > On 2018-02-11, Ral

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

Update with clang on Linux: sagelib ignores the --stdlib in CXX (#24705) and fpylll apparently ignores the --stdlib in CXX and if you give it in the CXXFLAGS it uses it only for C not C++ (#24707). So the former is a build blocker, the latter a critical because fpylll cannot be imported. I think

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

You're missing a devel system package. I have it in clang-devel and libc++-devel. On Sat, Feb 10, 2018 at 4:41 PM Simon King <simon.k...@uni-jena.de> wrote: > On 2018-02-10, Ralf Stephan <gtrw...@gmail.com> wrote: > > The linking error with --stdlib=libc++ persists.

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

bdl.so.2 (0x7f823d2fd000) libutil.so.1 => /lib64/libutil.so.1 (0x7f823d0fa000) https://trac.sagemath.org/ticket/24705 On Sat, Feb 10, 2018 at 3:43 PM Ralf Stephan <gtrw...@gmail.com> wrote: > Welcome to the bleeding edge. I'm afraid it won't work without > --stdlib=libc++

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

na.de> wrote: > Hi Ralf, > > On 2018-02-10, Ralf Stephan <gtrw...@gmail.com> wrote: > > Simon do you have libc++ system-installed and given CXX='clang++ > > --stdlib=libc++' ? > > No, I followed the previous advice to give CC=clan CXX=clan++. > > Does that

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

Simon do you have libc++ system-installed and given CXX='clang++ --stdlib=libc++' ? On Sat, Feb 10, 2018 at 1:15 PM Simon King wrote: > On 2018-02-10, Simon King wrote: > > On 2018-02-10, Simon King wrote: > >> Hi

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

FWIW for me as Pynac dev clang has far superior diagnostics and refactoring tools. From other programs I can confirm a speedup of compiled source of at least 5%. On Sat, Feb 10, 2018 at 9:55 AM François Bissey wrote: > > > > On 10/02/2018, at 21:44, Simon King

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

After building with clang on OpenSuSE two dozen doctests fail, all due to segfault in linbox: File "sage/matrix/matrix_modn_sparse.pyx", line 730, in sage.matrix.matrix_modn_sparse.Matrix_modn_sparse._rank_linbox (build/cythonized/sage/matrix/matrix_modn_sparse.c:9008) sig_on()

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

This is now https://trac.sagemath.org/ticket/24696 On Fri, Feb 9, 2018 at 3:35 PM Ralf Stephan <gtrw...@gmail.com> wrote: > Trying clang on Linux, after make distclean fails in giac but I'm not sure > if my installation is the reason. TLDR: > ./index.h:571:11: error: no template

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

Trying clang on Linux, after make distclean fails in giac but I'm not sure if my installation is the reason. TLDR: ./index.h:571:11: error: no template named 'hash_map' in namespace 'std'; did you mean '__gnu_cxx::hash_map'? giac compile log is attached -- You received this message because you

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

So how to use clang on Linux? On Fri, Feb 9, 2018 at 9:36 AM François Bissey wrote: > Note that from this release a fresh build on OS X will use clang. > Building gcc and using it can be triggered with SAGE_INSTALL_GCC=yes > as usual. > Incremental upgrade will continue to

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

I confirm that reinstalling internal gcc with 'sage -f gcc' makes giac compile without error. On Sun, Jan 28, 2018 at 8:53 AM Ralf Stephan <gtrw...@gmail.com> wrote: > That rather points to mpfr as the culprit IMHO. > > On Sun, Jan 28, 2018 at 8:43 AM François Bissey <fr

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

sage itself because > you have to > rebuild giac first). So I think giac may be using some mpfr construct > improperly or some > that should be private. > > François > > > On 28/01/2018, at 20:32, Ralf Stephan <gtrw...@gmail.com> wrote: > > > > How

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

rade as far > as I know. > All the other packages that depend on mpfr in sage don’t give rise to that > error. > > François > > > On 28/01/2018, at 20:19, Ralf Stephan <gtrw...@gmail.com> wrote: > > > > Doesn't this simply make internal gcc a dependency? If so then

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

Doesn't this simply make internal gcc a dependency? If so then is it enough to change that for the above ticket? On Sun, Jan 28, 2018 at 8:17 AM Ralf Stephan <gtrw...@gmail.com> wrote: > This is https://trac.sagemath.org/ticket/24599 > I'm trying now with the system gcc. > > On

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

s gcc - or use clang once support is merged :) > > François > > > On 28/01/2018, at 20:02, Ralf Stephan <gtrw...@gmail.com> wrote: > > > > Compiling giac with the gcc installed by Sage (7.2.0) gives an internal > compiler error: > > libtool: compile: g++ -DHAVE_C

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

Never mind, there was an isympy process taking it all, sorry for the noise. On Sat, Jan 20, 2018 at 5:25 PM Ralf Stephan <gtrw...@gmail.com> wrote: > I'm getting this on startup: > *** Warning: not enough memory, new stack 4470525952 > *** Warning: not enough memory, new s

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

I'm getting this on startup: *** Warning: not enough memory, new stack 4470525952 *** Warning: not enough memory, new stack 2235265024 *** Warning: not enough memory, new stack 1117634560 *** Warning: not enough memory, new stack 558817280 Everything else is normal. I have 32GB of

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

I get sage: Matrix(ZZ, sys.maxsize, sys.maxsize) Exception (FLINT memory_manager). Unable to allocate memory. RuntimeError: FLINT exception Seems signals are not caught on your system? On Sat, Dec 30, 2017 at 7:11 AM Dima Pasechnik wrote: > I am getting a segfault in

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

What could be the reason that for me the mirror search shows >5s ping for many mirrors, also for switch.ch which is always 20ms from here (and a manual ping confirms this)? -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from

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

The package can be downloaded manually at http://webusers.imj-prg.fr/~frederic.han/xcas/giacpy/sage/giacpy_sage-0.6.6.tar.gz That's the link given in https://trac.sagemath.org/ticket/23976 On Tue, Oct 17, 2017 at 3:32 PM Ralf Stephan <gtrw...@gmail.com> wrote: > Error downloading gi

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

Error downloading giacpy_sage-0.6.6.tar.gz The servers only have the previous 0.6 version. On Tue, Oct 17, 2017 at 8:56 AM Volker Braun wrote: > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source

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

On Wednesday, August 16, 2017 at 3:15:26 AM UTC+2, rich...@lozestech.com wrote: > > Under openSUSE LEAP 42.2, fresh git-clone + pull develop, all today, got > the following error during ptest (-j4): > Cannot confirm on openSUSE LEAP 42.2 using ten attempts of sage -tp

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

efore, needs work. But I'm not sure of this interpretation > (I do not (yet) understand) what the patchbot is supposed to do ; > therefore, I do not jnow if this is a patchbot error or a real problem with > the patch). > > -- > Emmanuel Charpentier > > > Le lundi 3 juillet 20

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

ImportError: cannot import name ContainChildren On Mon, Jul 3, 2017 at 4:56 PM Emmanuel Charpentier < emanuel.charpent...@gmail.com> wrote: > > > Le lundi 3 juillet 2017 15:58:31 UTC+2, Jeroen Demeyer a écrit : >> >> On 2017-07-02 10:38, Sébastien Labbé wrote: >> > See >> >

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

Ah ok there is still a -lmcheck somewhere from debugging, sry On Fri, Apr 28, 2017 at 8:33 AM Ralf Stephan <gtrw...@gmail.com> wrote: > I get this but maybe I messed up myself somewhere when switching between > debug yes/no: > > gcc

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

I get this but maybe I messed up myself somewhere when switching between debug yes/no: gcc version 5.4.0 (GCC) NOTE: Set SAGE_MATPLOTLIB_GUI to anything but 'no' to try to build the Matplotlib GUI. Not building any matplotlib graphical

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

Passes tests on OpenSuSE except the usual #21828, #22862, and some R fails I haven't reported yet. On Mon, Apr 24, 2017 at 6:03 AM Francois Bissey < francois.bis...@canterbury.ac.nz> wrote: > This is now https://trac.sagemath.org/ticket/22860 I should > have something ready in a few hours. > >

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

Confirmed. It was not there in the 8.0beta1 patchbot run: https://patchbot.sagemath.org/ticket/22090/ On Thu, Apr 13, 2017 at 2:22 PM Eric Gourgoulhon wrote: > From a fresh git clone + pull develop on Ubuntu 16.04 x86_64 i7-6700HQ + > 16 MB RAM, parallel (-j8) build OK.

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

Please followup at https://github.com/pynac/pynac/issues/231 On Wed, Feb 22, 2017 at 9:46 AM Jeroen Demeyer wrote: > I just noticed that this doctest was actually introduced in 7.6.beta4 in > #22174, so bisecting will not help... > > -- > You received this message

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

So gcc-6 is needed? I'm puzzled on what code change can trigger this. On Sat, Jan 7, 2017, 03:31 Francois Bissey wrote: > Looks like https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71767 > > François > > > On 7/01/2017, at 15:23, Justin C. Walker

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

Builds with 'make' upgrading from previous beta on OpenSuSE with SAGE_INSTALL_GCC=yes and passes 'make ptestlong' except for the apparently OpenSuSE-specific #21828. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group

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

On Fri, Nov 11, 2016 at 11:15 AM Emmanuel Charpentier < emanuel.charpent...@gmail.com> wrote: > On anothe machine (core17, 16 GB RAM, Debian testing) where I installed > giac in order to explore this > , I get > a failure of all

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

Right, that's it. Thanks, will recompile Singular. On Thu, Nov 10, 2016 at 5:15 PM Volker Braun <vbraun.n...@gmail.com> wrote: > Thats a SAGE_DEBUG=yes build of Singular, I presume. This is > https://trac.sagemath.org/ticket/21624 > > > On Thursday, November 10, 2016 at 5

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

Hi, I get reproducible doctest fails like this: File "src/sage/symbolic/relation.py", line 911, in sage.symbolic.relation.solve_mod Failed example: solve_mod([x^2 == 1, 4*x == 11], 15) Expected: [(14,)] Got: // ***dError: assume violation at numbers.cc:426 condition:

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

Hi, Regardless of the gcc used (Sage internal or not) both git master and develop crash in make ptestlong in combinat/posets/posets.py. Crash log is attached. The crash can be provoked interactively with: sage: Poset().is_incomparable_chain_free(1,1) ... -- You received this message because

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

https://trac.sagemath.org/ticket/21804 On Wed, Nov 2, 2016 at 8:22 PM Volker Braun <vbraun.n...@gmail.com> wrote: > open a ticket > > > On Wednesday, November 2, 2016 at 4:32:36 PM UTC+1, Ralf Stephan wrote: > > With this patch it all compiles: > diff --git a/src/sage

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

] intvec Is this known? Open ticket with it? On Wed, Nov 2, 2016 at 3:40 PM Ralf Stephan <gtrw...@gmail.com> wrote: > Again me with the gcc5 error on OpenSuSE, this time with serial log ;-) > > Thanks for any opinion, > -- You received this message because you are subscribed to

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

I get [sagelib-7.5.beta0] [ 7/298] gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrap v -O3 -Wall -Wno-unused -fPIC -I/home/ralf/sage/local/lib/python2.7/site-package s/cysignals -I/home/ralf/sage/local/include -I/home/ralf/sage/local/include/pyth on2.7

Re: [sage-release] Re: Sage 7.4.rc2 released

>So, a better question is: is there an estimate for how long a complete build, excluding or including documentation I don't care) should take on my machine (cpuinfo see above, using MAKE="make -j4"). My guess: more than two hours excluding documentation (where memory is important which info I

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

Fresh install on OpenSuSE-42.2beta. After switching from thir experimental gcc6 to gcc5 this: [sagelib-7.4.rc1] gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wno-unused -fPIC -I/home/ralf/sage/local/include -I/home/ralf/sage/local/includ e/python2.7

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

yer <jdeme...@cage.ugent.be> wrote: > On 2016-08-12 07:55, Ralf Stephan wrote: > > Not sure how new this is but I can no longer interrupt a Sage session > > with Ctrl-C > > Can you tell me *more precisely* what you're doing and how it doesn't > work anymore? > > -- > You

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

Not sure how new this is but I can no longer interrupt a Sage session with Ctrl-C which is necessary to get a gdb prompt. If new then presumably IPython the cause? I can workaround with Ctrl-Z and fg however. On Thu, Aug 11, 2016 at 10:55 PM Dima Pasechnik wrote: > After the

Re: [sage-release] Sage 7.3 released

On Fri, Aug 5, 2016 at 11:05 AM leif wrote: > No, the tombstones (or zombies?) are these: Huh. I just started work on one of these half an hour ago. So call me ghoul or ? -- You received this message because you are subscribed to the Google Groups "sage-release" group.

Re: [sage-release] 7.3.beta6

if it bothers you). On Fri, Jul 1, 2016 at 9:08 AM Ralf Stephan <gtrw...@gmail.com> wrote: > I don't get it. Why would the ao-devel pkg resolve the issue. Why don't > I get libao if I do > ralf@ark:~/sage> ldd local/lib/libgiac.so > on OpenSuSE? > > On Fri, Jul 1, 20

Re: [sage-release] 7.3.beta6

Or even add --with-giac=no in the Pynac spkg-install script. On Fri, Jul 1, 2016 at 8:55 AM Ralf Stephan <gtrw...@gmail.com> wrote: > > [pynac-0.6.7] /usr/bin/ld: cannot find -lao > > [pynac-0.6.7] collect2: error: ld returned 1 exit status > > No idea where you get that

Re: [sage-release] 7.3.beta6

> [pynac-0.6.7] /usr/bin/ld: cannot find -lao > [pynac-0.6.7] collect2: error: ld returned 1 exit status No idea where you get that library dependence from. What changed with beta5 was that if giac was installed that would be linked, so an experiment would be to uninstall giac and sage -p pynac

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

On OpenSuSE Leap it passes make ptestlong, with a few long test warnings. On Sat, May 7, 2016 at 2:26 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 >

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

Wrong. Additional directories in the Sage root are removed too, but not git repo directories. On Wed, Dec 23, 2015 at 9:00 AM Ralf Stephan <gtrw...@gmail.com> wrote: > On Tue, Dec 22, 2015 at 11:16 PM Volker Braun <vbraun.n...@gmail.com> > wrote: > >> Thats because &

Re: [sage-release] sagedev error

I did and Volker closed it already. But now I know that rerere was the reason here too. On Fri, Jul 17, 2015 at 10:16 AM Simon King simon.k...@uni-jena.de wrote: Hi! With rerere enabled in git (after a suggestion of Volker), I get Failed example: alice.pull() Expected: Merging the

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

A minimal set of changes is in http://trac.sagemath.org/ticket/18909 On Thu, Jul 16, 2015 at 9:53 AM Volker Braun vbraun.n...@gmail.com wrote: Probably due to #16124... Can you ellipsize the offending strings? On Thursday, July 16, 2015 at 9:42:39 AM UTC+2, Ralf Stephan wrote: make

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

make distclean; make; make ptestlong fails on OpenSuSE 13 with sage -t --long src/sage/dev/sagedev.py # 2 doctests failed File src/sage/dev/sagedev.py, line 1145, in sage.dev.sagedev.SageDev.pull Failed example: alice.pull() Expected: Merging the remote branch u/bob/ticket/1 into the

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

Ah no, never mind, sorry for spamming. On Fri, Jun 5, 2015 at 8:23 AM Ralf Stephan gtrw...@gmail.com wrote: Something changed with package tarball handling. My development tarballs of pynac in upstream/ are no longer found by ./sage -sh sage-fix-pkg-checksums and consequently Sage tries

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

Had to compile Atlas for three times in a row as well (beta4,5,6). Something wrong with upgrading? On Wed, Oct 15, 2014 at 8:47 AM, Emmanuel Charpentier emanuel.charpent...@gmail.com wrote: Did something change in Atlas ? On my fast machine (Core i7, 16 Gb RAM), going fro 6.4beta4 to

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

sage -t --long src/sage/stats/distributions/discrete_gaussian_integer.pyx ** File src/sage/stats/distributions/discrete_gaussian_integer.pyx, line 262, in

Re: [sage-release] Sage-6.3.beta7 released

Confirmed but for me it's (consistently) sage -t src/sage/graphs/generators/smallgraphs.py # 1 doctest failed sage -t src/sage/graphs/generators/families.py # 18 doctests failed sage -t src/sage/graphs/base/c_graph.pyx # 3 doctests failed sage -t src/sage/graphs/generators/intersection.py # 1

Re: [sage-release] Sage-6.3.beta7 released

On Tue, Jul 29, 2014 at 3:27 PM, Volker Braun vbraun.n...@gmail.com wrote: $SAGE_LOCAL/lib/libga ​p​ ​ralf@ark:~/sage l local/lib/libgap ls: cannot access local/lib/libgap: No such file or directory ​ -- You received this message because you are subscribed to the Google Groups sage-release

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

Is there a posting/page that lists what is needed to get rid of the expect interface? ​Wishful thinking at http://trac.sagemath.org/ticket/16688​ -- You received this message because you are subscribed to the Google Groups sage-release group. To unsubscribe from this group and stop

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

On 19 Jul 2014 14:14, Emmanuel Charpentier emanuel.charpent...@gmail.com wrote: make ptestlong got me one failure in src/sage/interfaces/expect.py at line 796. Doctesting it standalone (./sage -t --long src/sage/interfaces/expect.py ) was successful (All test passed!). Looks like a timeout due

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

On Thu, May 29, 2014 at 12:28 PM, Volker Braun vbraun.n...@gmail.comwrote: The reason is alarm() not working reliably. The failing test is from: 5159542 Trac #16162: Cantor-Zassenhaus may enter infinite loop over GF(2**k) and cannot be interrupted but thats just the symptom not the cause.

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

delivery to be 100% reliable On Thursday, May 29, 2014 2:34:13 PM UTC+1, Ralf Stephan wrote: On Thu, May 29, 2014 at 12:28 PM, Volker Braun vbrau...@gmail.comwrote: The reason is alarm() not working reliably. The failing test is from: 5159542 Trac #16162: Cantor-Zassenhaus may enter infinite

Re: [sage-release] Re: Sage 6.3.beta0

, but that ticket was merged in 6.3.beta0... Peter Op dinsdag 13 mei 2014 16:12:44 UTC+1 schreef Simon King: Hi Releasers, On 2014-05-11, Ralf Stephan gtr...@gmail.com wrote: I get doctest failures in dev/sagedev.py that go away when I switch to master and make, but won't go away

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

GIT_EXEC_PATH=/home/ralf/sage/local/libexec/git-core but git is in local/bin/? On Tue, May 13, 2014 at 5:46 PM, Simon King simon.k...@uni-jena.de wrote: Hi Volker, On 2014-05-13, Volker Braun vbraun.n...@gmail.com wrote: Get it from the updated develop git branch or the source tarball

[sage-release] Re: Sage 6.2.beta7 released

Barfs in make doc here (after make): -f local/etc/sage-started.txt ] || local/bin/sage-starts build/pipestatus ./sage --docbuild --no-pdf-links all html 21 tee -a logs/dochtml.log Traceback (most recent call last): File /home/ralf/sage/src/doc/common/builder.py, line 28, in module from