With Ubuntu 18.04, and running doctests with few optional/external
packages, I get:
--
sage -t --long --random-seed=4345853567077574058850080858948729205
src/sage/combinat/designs/incidence_structures.py # 1 doctest failed
sage
Thanks for the release. I am quite happy that #20343 is now in!
Testing on Ubuntu 18.04 with few optional and external packages, I get:
--
sage -t --long --random-seed=290149003222784740688944140527868655673
src/sage/combinat/de
On Ubuntu 18.04, running doctests with few optional and external tags, I
get:
Using
--optional=4ti2,build,ccache,cryptominisat,debian,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,lrslib,normaliz,notedown,pandoc_attributes,pip,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_c
Testing with few optional and external packages on Ubuntu 18.04, I get
failures with 8 files:
--
sage -t --long --random-seed=244716197900726204861772829584257473787
src/sage/tests/books/computational-mathematics-with-sagemath/l
Thanks for the release. On Ubuntu 18.04, with some optional and external
packages installed, I get:
--
sage -t --long --random-seed=10041023278531363329797553849793068311
src/sage/combinat/designs/incidence_structures.py # 1 do
Thanks for the release!
Sébastien
On Monday, May 16, 2022 at 12:27:40 AM UTC+2 Volker Braun wrote:
> The "master" git branch has been updated to Sage-9.6. As always, you can
> get the latest beta version from the "develop" git branch. Alternatively,
> the self-contained source tarball is at
>
On Ubuntu 20.04 + few optional packages, I get:
Using
--optional=4ti2,build,ccache,cryptominisat,debian,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,lrslib,normaliz,notedown,pandoc_attributes,pip,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_coin,sage_spkg
...
---
On Ubuntu 18.04, I get
Git branch: develop
Git ref: 9.7.beta3
Running with SAGE_LOCAL='/home/slabbe/GitBox/sage/local' and
SAGE_VENV='/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.10.3'
Using --optional=build,debian,external,pip,sage,sage_spkg
Features to be detected:
4ti2,benzene,bli
After upgrading my gcc, g++ and gfortran to 9, I managed to build and test
with a bunch of optional and external packages. I get the following list of
failures.
Using --optional=build,debian,external,glucose,pip,sage,sage_spkg
Features to be detected:
4ti2,benzene,bliss,buckygen,conway_polynomi
On a machine running Ubuntu 20.04 + some optional and external packages, I
obtain:
Using
--optional=4ti2,build,ccache,cryptominisat,debian,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,lrslib,normaliz,notedown,pandoc_attributes,pip,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backe
On Ubuntu 18.04, here is what I get with few optional/external packages:
Using --optional=build,debian,external,glucose,pip,sage,sage_spkg
Features to be detected:
4ti2,benzene,bliss,buckygen,conway_polynomials,cplex,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_he
On Ubuntu 18.04, with few optional/external packages, here is what I get:
Running with SAGE_LOCAL='/home/slabbe/GitBox/sage/local' and
SAGE_VENV='/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.10.8'
Using --optional=build,debian,external,glucose,pip,sage,sage_spkg
Features to be detecte
On Ubuntu 18.04 + optional packages, I get:
Using --optional=build,debian,dot2tex,external,glucose,pip,sage,sage_spkg
Features to be detected:
4ti2,benzene,bliss,buckygen,conway_polynomials,cplex,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_nu
On Ubuntu 18.04, I managed to make build and doc ok with cython
capabilities:
$ sage
┌┐
│ SageMath version 9.8.beta6, Release Date: 2022-12-21 │
│ Using Python 3.10.8. Type "help()" for help. │
Thanks for the release.
On my side, I am stuck with the following. I was having the same issue with
the previous version. I saw I was not alone, but I still don't know what is
the solution? Anybody know? Make distclean?
Sébastien
[sagelib-9.8.rc0] installing. Log file:
/home/slabbe/GitBox/sa
On another machine running Ubuntu 22.04, installing sage from source from
scratch, I get "m4: Permission denied" error during the "make configure".
Should I "sudo make configure" ? Never done that before...
See below:
$ make configure
./bootstrap -d
make[1] : on entre dans le répertoire « /home
On Thursday, February 2, 2023 at 6:31:21 PM UTC+1 John H Palmieri wrote:
Some people have had an issue with Singular: the system version is too new.
Using "./configure --with-system-singular=no" (probably after "make
distclean"?) would help, if that's the problem. There is an upgrade ticket
for
On Thursday, February 2, 2023 at 7:37:27 PM UTC+1 matthia...@gmail.com
wrote:
On Thursday, February 2, 2023 at 9:30:30 AM UTC-8 Sébastien Labbé wrote:
./bootstrap: 9: m4: Permission denied
make: *** [Makefile:365 : configure] Erreur 1
Do you have "." in PATH?
No
What does &quo
On Ubuntu 18.04, running tests with few optional and external packages, I
get:
Using
--optional=4ti2,antic,build,ccache,cryptominisat,debian,dot2tex,e_antic,external,fricas,glucose,latte_int,lidia,normaliz,notedown,pandoc_attributes,pip,pycosat,pynormaliz,rst2ipynb,sage,sage_numerical_backends_c
this is probably due to
https://github.com/sagemath/sage/pull/35093/commits/99901632beaa604331bca3d82eb5347bc43fc14e
Could you edit the corresponging installed file in local/ and see if
this starts passing.
If so, please open an issue.
I changed the false to true. The error is still there
On Ubuntu 18.04 with the following optional packages,
Using
--optional=4ti2,antic,build,cbc,ccache,cryptominisat,debian,dot2tex,e_antic,external,fricas,glucose,kissat,latte_int,lidia,normaliz,pip,sage,sage_numerical_backends_coin,sage_spkg
I get
On old Ubuntu 18.04, running tests with a bunch of optional/external
packages installed + internet, here is what I get:
Running with SAGE_LOCAL='/home/slabbe/GitBox/sage/local' and
SAGE_VENV='/home/slabbe/GitBox/sage/local/var/lib/sage/venv-python3.11.8'
Using
--optional=4ti2,build,cbc,ccache,
Bonjour sage-release,
On Wednesday, April 2, 2014 2:09:20 AM UTC+2, Volker Braun wrote:
>
> Get it from the "develop" git branch or the source tarball at
> http://boxen.math.washington.edu/home/release/sage-6.2.beta6/sage-6.2.beta6.tar.gz
>
I get an error while building matplotlib1-3.1. It seems
Hi sage-release,
I get an error with the compilation of sage/graphs/distances_all_pairs.c.
Here is what I did:
$ git checkout master
$ git pull --ff-only github master
$ make distclean
$ make
[...]
Host system:
Darwin pol 9.8.0 Darwin Kernel V
On Thursday, May 8, 2014 9:54:58 PM UTC+2, Peter Bruin wrote:
>
> Hello,
>
> It looks like (the automatically generated) distances_all_pairs.c is the
> result of an interrupted/failed Cython compilaton. My copy of that file is
> 14706 lines long and the last line is
>
> #endif /* Py_PYTHON_H *
$ make
[...]
Updating Cython code
Compiling sage/graphs/distances_all_pairs.pyx because it changed.
Found compiled sage/graphs/distances_all_pairs.pyx in cache
Finished Cythonizing, time: 10.05 seconds.
[...]
and then the same error again.
I need to delete the "compiled sage/graphs/distances_a
On Thursday, May 8, 2014 11:17:53 PM UTC+2, Peter Bruin wrote:
>
> The Cython cache seems to be ~/.cycache/, at least on my system.
>
thanks! now it works :
[...]
Updating Cython code
Compiling sage/graphs/distances_all_pairs.pyx because it changed.
Cythonizing sage/graphs/distances_all_pai
I get an error with libgd while compiling sage-6.6.rc2 on this machine:
$ uname -a
Darwin MacBookebastien.home 14.1.0 Darwin Kernel Version 14.1.0: Mon Dec 22
23:10:38 PST 2014; root:xnu-2782.10.72~2/RELEASE_X86_64 x86_64
Full libgd-2.1.0.p0.log is attached to this email. It finishes with:
mv -
On Wednesday, April 8, 2015 at 12:20:04 PM UTC+2, Volker Braun wrote:
>
> post the bzip2 install log
>
>>
>>
The bzip2 install log is attached. It was successful finishing with:
real0m16.313s
user0m12.348s
sys 0m7.020s
Successfully installed bzip2-1.0.6.20140317
Deleting tempora
On Wednesday, April 8, 2015 at 12:01:29 PM UTC+2, Sébastien Labbé wrote:
>
> I get an error with libgd while compiling sage-6.6.rc2 on this machine:
>
Maybe I have an hypothesis for this error... I am currently reinstalling
everything from scratch on my machine after I changed the hard
On Wednesday, April 8, 2015 at 1:35:04 PM UTC+2, Volker Braun wrote:
>
> bzip2 installed /Users/seb/Applications/sage/local/lib/libbz2.la, but it
> seems to be gone now. Who deleted it?
>
Nobody, it is still there. Thanks for the follow up. I now understand what
is happening. Not only I changed
> Let me recompile from scratch... I will give an update afterwards.
>
>
Testing that Sage starts...
[2015-04-09 19:47:34] Sage version 6.6.rc2, released 2015-04-02
Yes, Sage starts.
Sébastien
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
T
On ubuntu 14.04 64 bit make ptestlong gives 266 files with 1 failing
doctest, always the same warning:
sage -t --long src/doc/de/thematische_anleitungen/sage_gymnasium.rst
**
File "src/doc/de/thematische_anleitungen/sage_gymnasiu
On Thursday, April 16, 2015 at 11:05:11 AM UTC+2, Dima Pasechnik wrote:
>
> chmod 700 ~/.sage/.python-eggs
>
> should fix this
>
>
Indeed:
All tests passed!
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and
All tests passed with make ptestlong on ubuntu 14.04 x86_64.
Sébastien
--
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
On Ubuntu 14.04 64 bit, after make distclean, make ptestlong finishes with:
--
All tests passed!
--
Sébastien
--
You received this message because you are subsc
On Ubuntu 14.04 x86_64, after updating to github master and running make
distclean, sage-6.7 builds fine and starts, documentation builds fine but
make ptestlong finishes with 220 files having failing doctests all of them
related to missing optional package (I think make distclean removes them
On Tuesday, May 19, 2015 at 10:12:23 AM UTC+2, Jeroen Demeyer wrote:
>
> Did you run "make ptestlong" or "make ptestall"?
>
You are right. I did "make ptestall".
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group
Is there a way to "sage -i" all optional packages that are used the
doctests of the whole sage library?
Should "make ptestall" do that before running tests?
On Tuesday, May 19, 2015 at 10:17:17 AM UTC+2, Sébastien Labbé wrote:
>
>
>
> On Tuesday, May 19, 2
1 - On the first compilation, I get:
[algebras ] writing output... [ 96%]
sage/algebras/steenrod/steenrod_algebra_mult
[algebras ] writing output... [100%] sage/algebras/weyl_algebra
[algebras ] dumping object inventory... done
[algebras ] build succeeded.
[graphs ] reading sources... [ 73%] sa
Exactly, make doc-clean && make finishes with:
...
Elapsed time: 515.1 seconds.
Done building the documentation!
I understand that "sage -docbuild reference html" is not the way to go
anymore?
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To
Running make ptestlong on Ubuntu 14.04 and using
--optional=arb,benzene,bliss,buckygen,cbc,cryptominisat,database_cremona_ellcurve,database_gap,database_odlyzko_zeta,database_pari,database_stein_watkins,database_symbolic_data,dot2tex,gambit,gap_packages,gcc,gdb,mcqd,modular_decomposition,mpir,naut
>
> But the one in doctest/test.py keeps being there.
>
> --
> sage -t --long --warn-long 29.8 src/sage/doctest/test.py # 1 doctest
> failed
>
>
Needs review at:
http://trac.sagemath.org/ticket/18873
--
You received this m
On Ubuntu 14.04 64 bit and using
--optional=arb,benzene,bliss,buckygen,cbc,cryptominisat,database_cremona_ellcurve,database_gap,database_odlyzko_zeta,database_pari,database_stein_watkins,database_symbolic_data,dot2tex,gambit,gap_packages,gcc,gdb,mcqd,modular_decomposition,mpir,nauty,plantri,python
On OSX 10.10.2, Xcode 6.3, make ptestlong finishes with:
--
sage -t --long src/sage/doctest/test.py # Timed out after testing finished
--
which is not persisten
On Ubuntu 14.04 64 bit,
Using
--optional=arb,benzene,bliss,buckygen,cbc,coxeter3,cryptominisat,database_cremona_ellcurve,database_gap,database_odlyzko_zeta,database_pari,database_stein_watkins,database_symbolic_data,dot2tex,gambit,gap_packages,gcc,gdb,mcqd,modular_decomposition,mpir,nauty,plantri
--
which is not reproducible. Also, I confirm that I also get the display
latex problem cited above:
> ./sage -n jupyter
> In[1]: %display latex
> In[2]: sin(x^2)
> results in
> Out[2]: \newcommand{\Bold}[1]{\mathbf{#1}}\sin\left(x^{2}\right)
Sébastien Labbé
On Wednesday, October 7, 201
With optional sage packages coxeter3 and cryptominisat, I get some optional
doctests that are broken:
--
sage -t --warn-long 27.7
src/sage/rings/polynomial/multi_polynomial_sequence.py # 1 doctest failed
sage -t --warn-long 27.
On Friday, November 27, 2015 at 3:49:49 PM UTC+1, Sébastien Labbé wrote:
>
> With optional sage packages coxeter3 and cryptominisat, I get some
> optional doctests that are broken:
>
> --
> sage -t --warn-lon
Similarly,
sage: len(str('a'))
1
sage: len(repr('a'))
3
--
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 th
Hello patchbot developers,
At http://patchbot.sagemath.org/ticket/13580/, before the doctest
continuation problem was fixed, the patchbot was returning an incomplete
error message (see below). Maybe it would be better to
raise ValueError(full_msg.format(something here))
?
== plugins
Oups, I wanted to post this on sage-devel. Sorry.
Sébastien
On Tuesday, December 22, 2015 at 10:30:10 PM UTC+1, Sébastien Labbé wrote:
>
> Hello patchbot developers,
>
> At http://patchbot.sagemath.org/ticket/13580/, before the doctest
> continuation problem was fixed, t
I don't know if patchbots run make distclean but all of them report "Build
Failed" on 7.0.beta0 with the following error:
checking if g++ accepts -dumpversion option... yes
checking g++ version... 4.7.3
checking for sqrt in -lm... yes
checking package versions...
The content of "/home/worker/sag
On Wednesday, December 23, 2015 at 11:16:18 AM UTC+1, François wrote:
>
> It looks like one ticket for the packages of type `script` wasn’t included
> then.
>
But I can see that http://trac.sagemath.org/ticket/19427 merged in
sage-7.0.beta0 contains the diff:
- echo >&2 "The content of \"$PK
On Ubuntu 14.04 64 bit
Using --optional=gcc,mpir,python2,sage
make ptestlong finishes with
labbe@priminfo sage-git $ tail logs/ptestlong.log
sage -t --long --warn-long 27.1 src/sage_setup/docbuild/sphinxbuild.py
[0 tests, 0.00 s]
sage -t --long --warn-long 27.1 src/sage/schemes/toric/sheaf/
All tests passed on Ubuntu 14.04 with make ptestlong using
--optional=mpir,python2,sage
Other than the Tutte polynomial one, I get two other slow doctests that are
not marked with #long time. I can not confirm whether it is a regression as
I don't keep my old version of sage.
sage -t --long -
> -installed.update(pip_installed_packages())
> +# installed.update(pip_installed_packages())
>
I confirm that this change fixes the problem I mentionned earlier.
Sébastien
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsu
Using --optional=4ti2,atlas,mpir,python2,sage on Ubuntu 16.04
make ptestlong finishes with "All tests passed".
Thank you!
--
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
On Ubuntu 16.04,
Using --optional=4ti2,atlas,ccache,meataxe,mpir,pandocfilters,python2,sage
make ptestlong finishes with:
sage -t --long --warn-long 42.7 src/sage/matrix/matrix_integer_dense.pyx
Timed out (and interrupt failed)
*
On Ubuntu 16.04, running make ptestlong finishes with "Error installing
package openblas-0.2.19" with the following line in the openblas-0.2.19.log
./openblas_utest: error while loading shared libraries: libgfortran.so.3:
cannot open shared object file: No such file or directory
The end of the
On Wednesday, October 12, 2016 at 10:02:40 AM UTC+2, Jeroen Demeyer wrote:
>
>
> Thanks for your report. I saw this error on two of the patchbots too.
>
> Are you using the Sage-installed GCC package? What is the output of
>
> $ ./sage --sh -c 'which gfortran; gfortran --version'
>
$ ./sage -
On Wednesday, October 12, 2016 at 12:22:32 PM UTC+2, François wrote:
>
> I pushed a branch on that ticket to fix what I suspect is
> the problem.
> If it fixes it, I’ll push upstream since it is a problem
> in their default makefile.
>
>
Branch posted on #21689 fixes it! Thanks!
Sébastien
-
>From branch 7.4.rc0 + #21689, I checked out branch 7.4.rc1 and "make start"
works because "openblas" was not recompiled (why?).
But on branch 7.4.rc1, if I force compilation of openblas with "sage -f
openblas", then I get the same problem I reported yesterday in the 7.4.rc0
thread.
Therefore,
> Therefore, I will mark #21689 as a blocker so that it gets included in 7.4.
>
... I just realized Jeroen already set #21689 as blocker when he created
the ticket.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this gr
On Ubuntu 16.04, Using
--optional=4ti2,atlas,ccache,meataxe,mpir,pandoc_attributes,pandocfilters,python2,sage
make ptestlong finishes with
sage -t --long --warn-long 42.6 src/sage/modular/hecke/module.py
Timed out
**
Tests r
On Ubuntu 16.04, I get an error building the documentation (even after make
doc-clean && make):
[manifolds]
/home/labbe/Applications/sage-git/src/doc/en/reference/manifolds/index.rst:4:
WARNING: undefined label: tensors-on-free-modules (if the link has no
caption the label must precede a secti
On Tuesday, November 29, 2016 at 11:25:40 AM UTC+1, Sébastien Labbé wrote:
>
> On Ubuntu 16.04, I get an error building the documentation (even after
> make doc-clean && make):
>
I had uncommited changes in my repo (reverting cython version to 0.24 for
testing purposes
On OSX 10.10.2, I get two errors with make ptestlong (only the one with
singular.py reappears on a rerun) :
sage -t --long --warn-long 263.5 src/sage/misc/trace.py
**
File "src/sage/misc/trace.py", line 66, in sage.misc.trace.tra
On OS X 10.10.2, make ptestlong creates two sage.png file due to #21947 (I
will create a ticket to fix this shortly) and finishes with:
--
sage -t --long --warn-long 264.4 src/sage/modular/modform/element.py #
Timed out
sage -t
>
> make ptestlong creates two sage.png file due to #21947 (I will create a
> ticket to fix this shortly)
>
https://trac.sagemath.org/ticket/22009
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop rece
On OS X 10.10.2, make ptestlong has only one already reported failing test
( `sage126` is not defined line 514 in singular.py).
Also, I get a strange log file for sqlite which contains a little bit more
than the SPKG.txt file :
$ cat logs/pkgs/sqlite.log
Found local metadata for sqlite-autocon
Thank you very much Thierry. It was of great help during Sage Days 79.
I also used it recently on a old windows computer not connected to the
internet. It gives a second life to this machine:)
Sébastien
--
You received this message because you are subscribed to the Google Groups
"sage-releas
> Also, I get a strange log file for sqlite which contains a little bit more
> than the SPKG.txt file :
>
> $ cat logs/pkgs/sqlite.log
>
I found out that this junk file is created by sage -t
src/sage/tests/cmdline.py, I created:
https://trac.sagemath.org/ticket/22062
--
You received thi
> ImportError: No module named interpreters.wrapper_rdf
>
> Again, Eek!
> Justin
>
It was also reported in
Cannot build Sage 7.5.beta6 inside Docker, Dec 16, 2016
https://groups.google.com/d/topic/sage-devel/JkUfCPxoi80/discussion
The part " 'sage_setup.docbuild' is a package and cannot
On Ubuntu 16.04, git pull develop from 7.5.beta6 and make ptestlong has
only one failing (timed out) test:
sage: from sage.doctest.external import has_mathematica ## line 111 ##
sage: has_mathematica() # random ## line 112 ##
**
On Ubuntu 16.06, make ptestlong with MAKE="make j6" had one failing test
which I can not reproduce:
sage -t --long --warn-long 36.7 src/sage/homology/simplicial_complex.py
**
File "src/sage/homology/simplicial_complex.py", line 2
On Ubuntu 16.04, MAKE="make -j6" make ptestlong finishes with:
--
sage -t --long --warn-long 47.7 src/sage/homology/simplicial_complex.py #
1 doctest failed
sage -t --long --warn-long 47.7 src/sage/modular/abvar/homology.py # T
On Thursday, March 23, 2017 at 9:07:54 AM UTC+1, vdelecroix wrote:
>
> On 13/02/2017 14:32, Sébastien Labbé wrote:
> >
> > Also git status now tells me I have this file in SAGE_ROOT:
> >
> > octave-workspace
> >
> > ?
>
> How did you
On OSX 10.10 Yosemite, without #22860, make ptestlong yields only one
failed already reported doctest:
NotImplementedError: Unable to parse Giac output:
integrate(t^n*exp(-s*t),t,0,+infinity)
--
You received this message because you are subscribed to the Google Groups
"sage-release" grou
> Stupid question because I noticed stuff on the patchbot and so on.
> What happens if you do
> export LC_ALL=C
> before running the test?
>
$ export LC_ALL=C
$ sage -t --long src/sage/calculus/calculus.py
gives the same failed doctest.
Do yo mean
export LC_ALL=C
make ptestlong
?
--
Y
make ptestlong finishes with All tests passed! on Ubuntu 16.04.
--
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 pos
On osx 10.10, make ptestlong gives 2 doctest errors (which are not
reproducible):
sage -t --long src/sage/tests/cmdline.py
**
File "src/sage/tests/cmdline.py", line 208, in
sage.tests.cmdline.test_executable
Failed example:
On osx 10.10, make ptestlong gives: All test passed!
On Ubuntu 16.04, make ptestlong gives
--
sage -t --long --warn-long 61.1 src/sage/sat/boolean_polynomials.py # 1
doctest failed
---
> Thanks Volker! This is indeed the case: I've recently added the line
> %colors Linux
> to the file ~/.sage/init.sage
> Removing it fixes the problem.
>
It is better to set colors Linux in the file
profile_default/ipython_config.py
see
https://ask.sagemath.org/question/10060/sage-terminal-col
On Ubuntu 16.04, make ptestlong finishes with two doctest failures that
were already reported on this mailing list. Both doctests pass when run
separately.
--
sage -t --long --warn-long 61.4 src/sage/homology/simplicial_complex.
On Ubuntu 16.04, make ptestlong failed on building the documentation with
the following error:
Building reference manual, first pass.
Error building the documentation.
Traceback (most recent call last):
File "/home/slabbe/GitBox/sage/local/lib/python2.7/runpy.py", line 174,
in _run_module_as_
On a recent dell machine running Ubuntu 16.06, I get one failing test
during make ptestlong. The test pass when run alone :
sage -t --long src/sage/libs/gap/assigned_names.py
**
File "src/sage/libs/gap/assigned_names.py", line 5
On Ubuntu 16.04 make ptestlong gives All tests passed!
Thank you,
Sébastien
On Sunday, October 22, 2017 at 7:22:18 PM UTC+2, 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:/
On Ubuntu 16.04, I get problem building python2-2.7.14.p2 during make
ptestlong.
The error is reproducable when I perform sage -i python2
End of log is below
...
gcc -pthread -shared -L. -L/home/slabbe/GitBox/sage/local/lib
-Wl,-rpath,/home/slabbe/GitBox/sage/local/lib -L.
-L/home/slabbe/Gi
> ImportError: No module named _ctypes
> ctypes module failed to import
> math module imported OK
> hashlib module imported OK
> crypt module imported OK
> readline module imported OK
> socket module imported OK
> Error: One or more modules failed to import.
>
> real2m25.869s
> user2m5.51
... and I get "All tests passed!" after make ptestlong. Thank you.
--
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
I get 5 failing # optional - rst2ipynb doctests.
log below.
--
sage -t --long --warn-long 59.5 src/sage/tests/cmdline.py # 5 doctests
failed
--
sage -t --l
On Ubuntu 16.04, my first attempt at running make finishes with a problem
with giac (undefined reference to `png_set_longjmp_fn')
The log finishes with:
...
[giac-1.4.9.45.p2] libtool: link: g++ -g -O2 -fno-strict-aliasing
-DGIAC_GENERIC_CONSTANTS -Wl,-rpath -Wl,/home/slabbe/GitBox/sage/local/l
> ... still running.
>
> make ptestlong eventually finished with:
--
All tests passed!
--
--
You received this message because you are subscribed to the Googl
> this is a typical symptom of trying to link a wrong version of libpng.
>
Yes, but why does the `sage -f libpng` was not forced since it was
necessary? I am not an expert at all on this, but from my point of view, it
is like if there was problem with dependencies of giac.
>
> But what does
On Ubuntu 16.04, the command `./sage -t -p --all --long
--optional=sage,optional,external` finishes with:
--
sage -t --long src/sage/coding/code_constructions.py # 1 doctest failed
---
On Tuesday, May 15, 2018 at 9:24:26 PM UTC+2, Sébastien Labbé wrote:
>
> On Ubuntu 16.04, the command `./sage -t -p --all --long
> --optional=sage,optional,external` finishes with:
>
> --
> sage -t --lo
The first run of make gave the following error with gfan:
Found local metadata for gfan-0.6.2.p0
Traceback (most recent call last):
File "/home/slabbe/GitBox/sage/build/bin/sage-download-file", line 25, in
import sage_bootstrap
File "/home/slabbe/GitBox/sage/build/bin/../sage_bootstrap/
Running Ubuntu 16.06, I get
Using
--optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,mpir,notedown,pandoc_attributes,python2,rst2ipynb,sage
the command
./sage -t -p --all --long --optional=sage,optional,external --show-skipped
--logfile=logs/ptestallshowskipped.log
gives:
--
The command:
./sage -t -p --all --long --optional=sage,optional,external
Using
--optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,notedown,pandoc_attributes,python2,rst2ipynb,sage
External software detected for doctesting:
ffmpeg,graphviz,gurobi,imagemagick,internet,l
101 - 200 of 243 matches
Mail list logo
