[sage-release] Re: Sage 9.0.beta6 released
I reported similar problems since I started to use ptestalllong on Python3-based Sagemath. In the present case, I just checked that *each* of these tests passes when (manually) ran standalone. Since - I get the same problems when running testallong (i. e. nnot* parallel), - the lis of your problrmatic test only partially intersects mine, I think that the problem is with the test infrastructure. HTH, Le mardi 19 novembre 2019 09:26:48 UTC+1, Sébastien Labbé a écrit : > > > Running ptestlong with optional + external packages, I get > > Using > --optional=4ti2,cbc,ccache,cryptominisat,dot2tex,e_antic,external,glucose,latte_int,lidia,lrslib,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,rst2ipynb,sage,sagenb > > -- > sage -t --long src/doc/en/thematic_tutorials/linear_programming.rst # 1 > doctest failed > sage -t --long src/sage/coding/databases.py # 2 doctests failed > sage -t --long src/sage/combinat/matrices/hadamard_matrix.py # 2 doctests > failed > sage -t --long src/sage/combinat/posets/posets.py # 1 doctest failed > sage -t --long src/sage/databases/findstat.py # 9 doctests failed > sage -t --long src/sage/graphs/graph_latex.py # 2 doctests failed > sage -t --long src/sage/misc/latex.py # 1 doctest failed > sage -t --long src/sage/misc/persist.pyx # 2 doctests failed > sage -t --long src/sage/misc/remote_file.py # 2 doctests failed > sage -t --long src/sage/numerical/backends/gurobi_backend.pyx # 17 > doctests failed > sage -t --long src/sage/numerical/linear_functions.pyx # 29 doctests > failed > sage -t --long src/sage/numerical/linear_tensor.py # 20 doctests failed > sage -t --long src/sage/numerical/linear_tensor_constraints.py # 28 > doctests failed > sage -t --long src/sage/numerical/linear_tensor_element.pyx # 23 doctests > failed > sage -t --long src/sage/numerical/mip.pyx # 4 doctests failed > sage -t --long src/sage/plot/animate.py # 7 doctests failed > sage -t --long src/sage/repl/load.py # 1 doctest failed > sage -t --long src/sage/sat/solvers/dimacs.py # 7 doctests failed > sage -t --long src/sage/tests/cmdline.py # 2 doctests failed > -- > External software detected for doctesting: > ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc > > Reruning the failed tests, I obtain the same: > > -- > sage -t --long src/doc/en/thematic_tutorials/linear_programming.rst # 1 > doctest failed > sage -t --long src/sage/coding/databases.py # 2 doctests failed > sage -t --long src/sage/combinat/matrices/hadamard_matrix.py # 2 doctests > failed > sage -t --long src/sage/combinat/posets/posets.py # 1 doctest failed > sage -t --long src/sage/databases/findstat.py # 9 doctests failed > sage -t --long src/sage/graphs/graph_latex.py # 2 doctests failed > sage -t --long src/sage/misc/latex.py # 1 doctest failed > sage -t --long src/sage/misc/persist.pyx # 2 doctests failed > sage -t --long src/sage/misc/remote_file.py # 2 doctests failed > sage -t --long src/sage/numerical/backends/gurobi_backend.pyx # 17 > doctests failed > sage -t --long src/sage/numerical/linear_functions.pyx # 29 doctests > failed > sage -t --long src/sage/numerical/linear_tensor.py # 20 doctests failed > sage -t --long src/sage/numerical/linear_tensor_constraints.py # 28 > doctests failed > sage -t --long src/sage/numerical/linear_tensor_element.pyx # 23 doctests > failed > sage -t --long src/sage/numerical/mip.pyx # 4 doctests failed > sage -t --long src/sage/plot/animate.py # 7 doctests failed > sage -t --long src/sage/repl/load.py # 1 doctest failed > sage -t --long src/sage/sat/solvers/dimacs.py # 7 doctests failed > sage -t --long src/sage/tests/cmdline.py # 2 doctests failed > -- > External software detected for doctesting: > ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc > > A bunch of new tickets are to be created. Follow up at > https://trac.sagemath.org/ticket/25536 > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/5c9ba2a1-eb7a-4748-a226-e45f4dfdcf32%40googlegroups.com.
Re: [sage-release] Re: Sage 9.0.beta6 released
The problems with incremental building and Python 2 vs. Python 3 are being tracked at https://trac.sagemath.org/ticket/28742 On Tuesday, November 19, 2019 at 6:57:36 AM UTC-8, Dima Pasechnik wrote: > > On Tue, Nov 19, 2019 at 1:59 PM E. Madison Bray > wrote: > > > > On Tue, Nov 19, 2019 at 2:55 PM E. Madison Bray > wrote: > > > > > > On Mon, Nov 18, 2019 at 3:51 PM Sébastien Labbé > wrote: > > > > > > > > > > > > > > > > > > > > The first try at running make gives me this: > > > > > > > > > > > > [sagelib-9.0.beta6] make[4] : on entre dans le répertoire « > /home/slabbe/GitBox/sage/src » > > > > [sagelib-9.0.beta6] cd . && export > \ > > > > [sagelib-9.0.beta6] SAGE_ROOT=/doesnotexist > \ > > > > [sagelib-9.0.beta6] SAGE_SRC=/doesnotexist > \ > > > > [sagelib-9.0.beta6] SAGE_SRC_ROOT=/doesnotexist > \ > > > > [sagelib-9.0.beta6] SAGE_DOC_SRC=/doesnotexist > \ > > > > [sagelib-9.0.beta6] SAGE_BUILD_DIR=/doesnotexist > \ > > > > [sagelib-9.0.beta6] > SAGE_PKGS=/home/slabbe/GitBox/sage/build/pkgs\ > > > > [sagelib-9.0.beta6] && sage-python -u setup.py --no-user-cfg build > install > > > > [sagelib-9.0.beta6] /home/slabbe/GitBox/sage/src/bin/sage-env: ligne > 130 : cd: /doesnotexist: Aucun fichier ou dossier de ce type > > > > [sagelib-9.0.beta6] Warning: overwriting SAGE_ROOT environment > variable: > > > > [sagelib-9.0.beta6] Old SAGE_ROOT=/doesnotexist > > > > [sagelib-9.0.beta6] New SAGE_ROOT= > > > > [sagelib-9.0.beta6] Traceback (most recent call last): > > > > [sagelib-9.0.beta6] File "setup.py", line 22, in > > > > [sagelib-9.0.beta6] import fpickle_setup > > > > [sagelib-9.0.beta6] File > "/home/slabbe/GitBox/sage/src/fpickle_setup.py", line 8, in > > > > [sagelib-9.0.beta6] from six.moves import copyreg > > > > [sagelib-9.0.beta6] ModuleNotFoundError: No module named 'six' > > > > [sagelib-9.0.beta6] Makefile:33 : la recette pour la cible « sage » > a échouée > > > > [sagelib-9.0.beta6] make[4]: *** [sage] Erreur 1 > > > > [sagelib-9.0.beta6] make[4] : on quitte le répertoire « > /home/slabbe/GitBox/sage/src » > > > > [sagelib-9.0.beta6] > > > > [sagelib-9.0.beta6] real0m0.049s > > > > [sagelib-9.0.beta6] user0m0.032s > > > > [sagelib-9.0.beta6] sys0m0.012s > > > > Makefile:1987 : la recette pour la cible « sagelib » a échouée > > > > make[3]: *** [sagelib] Erreur 2 > > > > make[3] : on quitte le répertoire « > /home/slabbe/GitBox/sage/build/make » > > > > Makefile:1848 : la recette pour la cible « all-start » a échouée > > > > make[2]: *** [all-start] Erreur 2 > > > > make[2] : on quitte le répertoire « > /home/slabbe/GitBox/sage/build/make » > > > > > > > > real0m0.208s > > > > user0m0.148s > > > > sys0m0.016s > > > > *** > > > > Error building Sage. > > > > > > > > The following package(s) may have failed to build (not necessarily > > > > during this run of 'make all-start'): > > > > > > > > The build directory may contain configuration files and other > potentially > > > > helpful information. WARNING: if you now run 'make' again, the build > > > > directory will, by default, be deleted. Set the environment variable > > > > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. > > > > > > IMO this does appear to be a bug though. If you have an existing > > > Python 2 build of Sage it should *not* break just because the default > > > has changed to Python 3. It appears something is trying to run the > > > fpickle_setup.py script (whatever that is) with python3 even if it's a > > > python2 build of Sage. > > > > Nevermind--the real issue is the opposite of what I wrote two posts > > ago. If you have a python2 build of Sage and you want to keep it as > > python2 you need to do a `./configure --with-python=2`. It's kind of > > annoying that this is not preserved (I'm a little confused that it > > isn't, since I thought that was the point of having config.status...) > > isn't config.status a script, to re-create/show the current configuration? > So you'd run > ./config-status --config to see the confugure's parameters used > at its last call. > > > > > -- > > 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-r...@googlegroups.com . > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/CAOTD34a%2BQ9tWiEMN325KKxfdYoDXj3XF-QEmLxvWh5kQqP1xyQ%40mail.gmail.com. > > > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving
Re: [sage-release] Re: Sage 9.0.beta6 released
On Tue, Nov 19, 2019 at 1:59 PM E. Madison Bray wrote: > > On Tue, Nov 19, 2019 at 2:55 PM E. Madison Bray wrote: > > > > On Mon, Nov 18, 2019 at 3:51 PM Sébastien Labbé wrote: > > > > > > > > > > > > > > > The first try at running make gives me this: > > > > > > > > > [sagelib-9.0.beta6] make[4] : on entre dans le répertoire « > > > /home/slabbe/GitBox/sage/src » > > > [sagelib-9.0.beta6] cd . && export\ > > > [sagelib-9.0.beta6] SAGE_ROOT=/doesnotexist > > > \ > > > [sagelib-9.0.beta6] SAGE_SRC=/doesnotexist > > > \ > > > [sagelib-9.0.beta6] SAGE_SRC_ROOT=/doesnotexist > > > \ > > > [sagelib-9.0.beta6] SAGE_DOC_SRC=/doesnotexist > > > \ > > > [sagelib-9.0.beta6] SAGE_BUILD_DIR=/doesnotexist > > > \ > > > [sagelib-9.0.beta6] SAGE_PKGS=/home/slabbe/GitBox/sage/build/pkgs > > >\ > > > [sagelib-9.0.beta6] && sage-python -u setup.py --no-user-cfg build install > > > [sagelib-9.0.beta6] /home/slabbe/GitBox/sage/src/bin/sage-env: ligne 130 > > > : cd: /doesnotexist: Aucun fichier ou dossier de ce type > > > [sagelib-9.0.beta6] Warning: overwriting SAGE_ROOT environment variable: > > > [sagelib-9.0.beta6] Old SAGE_ROOT=/doesnotexist > > > [sagelib-9.0.beta6] New SAGE_ROOT= > > > [sagelib-9.0.beta6] Traceback (most recent call last): > > > [sagelib-9.0.beta6] File "setup.py", line 22, in > > > [sagelib-9.0.beta6] import fpickle_setup > > > [sagelib-9.0.beta6] File > > > "/home/slabbe/GitBox/sage/src/fpickle_setup.py", line 8, in > > > [sagelib-9.0.beta6] from six.moves import copyreg > > > [sagelib-9.0.beta6] ModuleNotFoundError: No module named 'six' > > > [sagelib-9.0.beta6] Makefile:33 : la recette pour la cible « sage » a > > > échouée > > > [sagelib-9.0.beta6] make[4]: *** [sage] Erreur 1 > > > [sagelib-9.0.beta6] make[4] : on quitte le répertoire « > > > /home/slabbe/GitBox/sage/src » > > > [sagelib-9.0.beta6] > > > [sagelib-9.0.beta6] real0m0.049s > > > [sagelib-9.0.beta6] user0m0.032s > > > [sagelib-9.0.beta6] sys0m0.012s > > > Makefile:1987 : la recette pour la cible « sagelib » a échouée > > > make[3]: *** [sagelib] Erreur 2 > > > make[3] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make » > > > Makefile:1848 : la recette pour la cible « all-start » a échouée > > > make[2]: *** [all-start] Erreur 2 > > > make[2] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make » > > > > > > real0m0.208s > > > user0m0.148s > > > sys0m0.016s > > > *** > > > Error building Sage. > > > > > > The following package(s) may have failed to build (not necessarily > > > during this run of 'make all-start'): > > > > > > The build directory may contain configuration files and other potentially > > > helpful information. WARNING: if you now run 'make' again, the build > > > directory will, by default, be deleted. Set the environment variable > > > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. > > > > IMO this does appear to be a bug though. If you have an existing > > Python 2 build of Sage it should *not* break just because the default > > has changed to Python 3. It appears something is trying to run the > > fpickle_setup.py script (whatever that is) with python3 even if it's a > > python2 build of Sage. > > Nevermind--the real issue is the opposite of what I wrote two posts > ago. If you have a python2 build of Sage and you want to keep it as > python2 you need to do a `./configure --with-python=2`. It's kind of > annoying that this is not preserved (I'm a little confused that it > isn't, since I thought that was the point of having config.status...) isn't config.status a script, to re-create/show the current configuration? So you'd run ./config-status --config to see the confugure's parameters used at its last call. > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/CAOTD34a%2BQ9tWiEMN325KKxfdYoDXj3XF-QEmLxvWh5kQqP1xyQ%40mail.gmail.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/CAAWYfq2MZgSY6MAkbCMGL2_wycBFQgaGPQ0jjg0XxHPp12q2Ag%40mail.gmail.com.
Re: [sage-release] Re: Sage 9.0.beta6 released
On Tue, Nov 19, 2019 at 2:55 PM E. Madison Bray wrote: > > On Mon, Nov 18, 2019 at 3:51 PM Sébastien Labbé wrote: > > > > > > > > > > The first try at running make gives me this: > > > > > > [sagelib-9.0.beta6] make[4] : on entre dans le répertoire « > > /home/slabbe/GitBox/sage/src » > > [sagelib-9.0.beta6] cd . && export\ > > [sagelib-9.0.beta6] SAGE_ROOT=/doesnotexist > > \ > > [sagelib-9.0.beta6] SAGE_SRC=/doesnotexist > > \ > > [sagelib-9.0.beta6] SAGE_SRC_ROOT=/doesnotexist > > \ > > [sagelib-9.0.beta6] SAGE_DOC_SRC=/doesnotexist > > \ > > [sagelib-9.0.beta6] SAGE_BUILD_DIR=/doesnotexist > > \ > > [sagelib-9.0.beta6] SAGE_PKGS=/home/slabbe/GitBox/sage/build/pkgs > > \ > > [sagelib-9.0.beta6] && sage-python -u setup.py --no-user-cfg build install > > [sagelib-9.0.beta6] /home/slabbe/GitBox/sage/src/bin/sage-env: ligne 130 : > > cd: /doesnotexist: Aucun fichier ou dossier de ce type > > [sagelib-9.0.beta6] Warning: overwriting SAGE_ROOT environment variable: > > [sagelib-9.0.beta6] Old SAGE_ROOT=/doesnotexist > > [sagelib-9.0.beta6] New SAGE_ROOT= > > [sagelib-9.0.beta6] Traceback (most recent call last): > > [sagelib-9.0.beta6] File "setup.py", line 22, in > > [sagelib-9.0.beta6] import fpickle_setup > > [sagelib-9.0.beta6] File "/home/slabbe/GitBox/sage/src/fpickle_setup.py", > > line 8, in > > [sagelib-9.0.beta6] from six.moves import copyreg > > [sagelib-9.0.beta6] ModuleNotFoundError: No module named 'six' > > [sagelib-9.0.beta6] Makefile:33 : la recette pour la cible « sage » a > > échouée > > [sagelib-9.0.beta6] make[4]: *** [sage] Erreur 1 > > [sagelib-9.0.beta6] make[4] : on quitte le répertoire « > > /home/slabbe/GitBox/sage/src » > > [sagelib-9.0.beta6] > > [sagelib-9.0.beta6] real0m0.049s > > [sagelib-9.0.beta6] user0m0.032s > > [sagelib-9.0.beta6] sys0m0.012s > > Makefile:1987 : la recette pour la cible « sagelib » a échouée > > make[3]: *** [sagelib] Erreur 2 > > make[3] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make » > > Makefile:1848 : la recette pour la cible « all-start » a échouée > > make[2]: *** [all-start] Erreur 2 > > make[2] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make » > > > > real0m0.208s > > user0m0.148s > > sys0m0.016s > > *** > > Error building Sage. > > > > The following package(s) may have failed to build (not necessarily > > during this run of 'make all-start'): > > > > The build directory may contain configuration files and other potentially > > helpful information. WARNING: if you now run 'make' again, the build > > directory will, by default, be deleted. Set the environment variable > > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. > > IMO this does appear to be a bug though. If you have an existing > Python 2 build of Sage it should *not* break just because the default > has changed to Python 3. It appears something is trying to run the > fpickle_setup.py script (whatever that is) with python3 even if it's a > python2 build of Sage. Nevermind--the real issue is the opposite of what I wrote two posts ago. If you have a python2 build of Sage and you want to keep it as python2 you need to do a `./configure --with-python=2`. It's kind of annoying that this is not preserved (I'm a little confused that it isn't, since I thought that was the point of having config.status...) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/CAOTD34a%2BQ9tWiEMN325KKxfdYoDXj3XF-QEmLxvWh5kQqP1xyQ%40mail.gmail.com.
Re: [sage-release] Re: Sage 9.0.beta6 released
On Mon, Nov 18, 2019 at 3:51 PM Sébastien Labbé wrote: > > > > > The first try at running make gives me this: > > > [sagelib-9.0.beta6] make[4] : on entre dans le répertoire « > /home/slabbe/GitBox/sage/src » > [sagelib-9.0.beta6] cd . && export\ > [sagelib-9.0.beta6] SAGE_ROOT=/doesnotexist > \ > [sagelib-9.0.beta6] SAGE_SRC=/doesnotexist > \ > [sagelib-9.0.beta6] SAGE_SRC_ROOT=/doesnotexist > \ > [sagelib-9.0.beta6] SAGE_DOC_SRC=/doesnotexist > \ > [sagelib-9.0.beta6] SAGE_BUILD_DIR=/doesnotexist > \ > [sagelib-9.0.beta6] SAGE_PKGS=/home/slabbe/GitBox/sage/build/pkgs >\ > [sagelib-9.0.beta6] && sage-python -u setup.py --no-user-cfg build install > [sagelib-9.0.beta6] /home/slabbe/GitBox/sage/src/bin/sage-env: ligne 130 : > cd: /doesnotexist: Aucun fichier ou dossier de ce type > [sagelib-9.0.beta6] Warning: overwriting SAGE_ROOT environment variable: > [sagelib-9.0.beta6] Old SAGE_ROOT=/doesnotexist > [sagelib-9.0.beta6] New SAGE_ROOT= > [sagelib-9.0.beta6] Traceback (most recent call last): > [sagelib-9.0.beta6] File "setup.py", line 22, in > [sagelib-9.0.beta6] import fpickle_setup > [sagelib-9.0.beta6] File "/home/slabbe/GitBox/sage/src/fpickle_setup.py", > line 8, in > [sagelib-9.0.beta6] from six.moves import copyreg > [sagelib-9.0.beta6] ModuleNotFoundError: No module named 'six' > [sagelib-9.0.beta6] Makefile:33 : la recette pour la cible « sage » a échouée > [sagelib-9.0.beta6] make[4]: *** [sage] Erreur 1 > [sagelib-9.0.beta6] make[4] : on quitte le répertoire « > /home/slabbe/GitBox/sage/src » > [sagelib-9.0.beta6] > [sagelib-9.0.beta6] real0m0.049s > [sagelib-9.0.beta6] user0m0.032s > [sagelib-9.0.beta6] sys0m0.012s > Makefile:1987 : la recette pour la cible « sagelib » a échouée > make[3]: *** [sagelib] Erreur 2 > make[3] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make » > Makefile:1848 : la recette pour la cible « all-start » a échouée > make[2]: *** [all-start] Erreur 2 > make[2] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make » > > real0m0.208s > user0m0.148s > sys0m0.016s > *** > Error building Sage. > > The following package(s) may have failed to build (not necessarily > during this run of 'make all-start'): > > The build directory may contain configuration files and other potentially > helpful information. WARNING: if you now run 'make' again, the build > directory will, by default, be deleted. Set the environment variable > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. IMO this does appear to be a bug though. If you have an existing Python 2 build of Sage it should *not* break just because the default has changed to Python 3. It appears something is trying to run the fpickle_setup.py script (whatever that is) with python3 even if it's a python2 build of Sage. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/CAOTD34Zr2Een8%2Bvoj%2Bim%3DpP6o_Xm4P6BFZarZ1uDzXa8rc58Wg%40mail.gmail.com.
Re: [sage-release] Re: Sage 9.0.beta6 released
On Mon, Nov 18, 2019 at 9:31 PM darwin doppelganger wrote: > > I did a "make distclean" followed by "make" on my Mac OSX 10.14.6, Xcode > 11.2.1 and the build completed successfully: It's not even necessary to do a full `make distclean`. Instead you have to manually reconfigure your build to use --with-python=3 like $ ./configure --with-python=3 *then* $ make >> [2019-11-18 14:22:10] SageMath version 9.0.beta6, Release Date: 2019-11-18 >> Yes, Sage starts. >> real257m11.634s >> user280m20.436s >> sys 31m35.438s >> Sage build/upgrade complete! > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/3bc5756c-679b-4525-be49-b587b5151de1%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/CAOTD34ZwHZvxy3gNCWjvY9hnfnPam23watd8%2BtUw2aUpomnz7g%40mail.gmail.com.
Re: [sage-release] Sage 9.0.beta6 released
> On Nov 17, 2019, at 16:42 , 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 > > This is the first Python 3 beta, so incremental builds probably aren't going > to work. Use "make distclean" or the appropriate configure flag to keep using > Python 2 (n) Built w/o problems on three macOS systems: 10.11.6 (mid-2015 MBP, Quad-core Core i7), 10.13.6 (2017 iMac Pro, 18-core Xeon W), and 10.14.6 (2017 MBP, Quad-core Core i7). Testing showed the following failures: 10.11.6: sage -t --long --warn-long 98.8 src/sage/symbolic/expression.pyx # 2 doctests failed sage -t --long --warn-long 98.8 src/sage/misc/sageinspect.py # 4 doctests failed sage -t --long --warn-long 98.8 src/sage/repl/ipython_extension.py # 2 doctests failed Of the three, the first is transient; and the latter two appear to be repeatable: multiple test runs of these two failed consistently. 10.13.6: sage -t --long --warn-long 72.2 src/sage/groups/cubic_braid.py # 1 doctest failed This is transient. 10.14.6: sage -t --long --warn-long 80.8 src/sage/symbolic/expression.pyx This is transient. Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds --- My wife 'n kids 'n dogs are gone, I can't get Jesus on the phone, But Ol' Milwaukee's Best is my best friend. --- -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/F74E69C6-53B5-46BB-BA6D-F1590972B3F2%40mac.com.
[sage-release] Re: Sage 9.0.beta6 released
Running ptestlong with optional + external packages, I get Using --optional=4ti2,cbc,ccache,cryptominisat,dot2tex,e_antic,external,glucose,latte_int,lidia,lrslib,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,rst2ipynb,sage,sagenb -- sage -t --long src/doc/en/thematic_tutorials/linear_programming.rst # 1 doctest failed sage -t --long src/sage/coding/databases.py # 2 doctests failed sage -t --long src/sage/combinat/matrices/hadamard_matrix.py # 2 doctests failed sage -t --long src/sage/combinat/posets/posets.py # 1 doctest failed sage -t --long src/sage/databases/findstat.py # 9 doctests failed sage -t --long src/sage/graphs/graph_latex.py # 2 doctests failed sage -t --long src/sage/misc/latex.py # 1 doctest failed sage -t --long src/sage/misc/persist.pyx # 2 doctests failed sage -t --long src/sage/misc/remote_file.py # 2 doctests failed sage -t --long src/sage/numerical/backends/gurobi_backend.pyx # 17 doctests failed sage -t --long src/sage/numerical/linear_functions.pyx # 29 doctests failed sage -t --long src/sage/numerical/linear_tensor.py # 20 doctests failed sage -t --long src/sage/numerical/linear_tensor_constraints.py # 28 doctests failed sage -t --long src/sage/numerical/linear_tensor_element.pyx # 23 doctests failed sage -t --long src/sage/numerical/mip.pyx # 4 doctests failed sage -t --long src/sage/plot/animate.py # 7 doctests failed sage -t --long src/sage/repl/load.py # 1 doctest failed sage -t --long src/sage/sat/solvers/dimacs.py # 7 doctests failed sage -t --long src/sage/tests/cmdline.py # 2 doctests failed -- External software detected for doctesting: ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc Reruning the failed tests, I obtain the same: -- sage -t --long src/doc/en/thematic_tutorials/linear_programming.rst # 1 doctest failed sage -t --long src/sage/coding/databases.py # 2 doctests failed sage -t --long src/sage/combinat/matrices/hadamard_matrix.py # 2 doctests failed sage -t --long src/sage/combinat/posets/posets.py # 1 doctest failed sage -t --long src/sage/databases/findstat.py # 9 doctests failed sage -t --long src/sage/graphs/graph_latex.py # 2 doctests failed sage -t --long src/sage/misc/latex.py # 1 doctest failed sage -t --long src/sage/misc/persist.pyx # 2 doctests failed sage -t --long src/sage/misc/remote_file.py # 2 doctests failed sage -t --long src/sage/numerical/backends/gurobi_backend.pyx # 17 doctests failed sage -t --long src/sage/numerical/linear_functions.pyx # 29 doctests failed sage -t --long src/sage/numerical/linear_tensor.py # 20 doctests failed sage -t --long src/sage/numerical/linear_tensor_constraints.py # 28 doctests failed sage -t --long src/sage/numerical/linear_tensor_element.pyx # 23 doctests failed sage -t --long src/sage/numerical/mip.pyx # 4 doctests failed sage -t --long src/sage/plot/animate.py # 7 doctests failed sage -t --long src/sage/repl/load.py # 1 doctest failed sage -t --long src/sage/sat/solvers/dimacs.py # 7 doctests failed sage -t --long src/sage/tests/cmdline.py # 2 doctests failed -- External software detected for doctesting: ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc A bunch of new tickets are to be created. Follow up at https://trac.sagemath.org/ticket/25536 -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/77680439-4405-4b4f-b8fb-595f6de2be7f%40googlegroups.com.
