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
> 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
>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,
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
-
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 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 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)
*
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
> -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
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 -
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/
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
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
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
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
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
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
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.
--
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
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
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 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
>
> 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
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
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
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
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
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
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 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
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 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
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
> 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 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
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 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
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 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
$ 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 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 *
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
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
201 - 243 of 243 matches
Mail list logo
