The Maxima error is http://trac.sagemath.org/ticket/17667. This seems to be
a serious bug in the new Maxima version.
On Tuesday, January 6, 2015 at 2:50:40 AM UTC+1, John H Palmieri wrote:
>
> On Monday, January 5, 2015 2:38:41 PM UTC-8, Volker Braun wrote:
>>
>> As usual, get the "develop" bra
The former is now #17666 (needs review)
On Tuesday, January 6, 2015 at 2:50:40 AM UTC+1, John H Palmieri wrote:
>
> sage -t --long --warn-long 38.0 src/sage/libs/singular/polynomial.pyx # 1
> doctest failed
>
--
You received this message because you are subscribed to the Google Groups
"sage-r
Marc Mezzarobba wrote:
> the build scripts of some spkgs [...]
> were using the system-wide version of setuptools (namely
> python-setuptools-5.5.1-1 from debian sid) rather than the version
> shipped with sage.
Ok, I think I found the culprit: some other Python library I had
installed had put a
Hi,
I'm having trouble building 6.4.beta5 from a clean git checkout
on debian sid. Unfortunately, I no longer have the logs, but it
looked like the build scripts of some spkgs, including at least
jinja2, were using the system-wide version of setuptools (namely
python-setuptools-5.5.1-1 from debian
On Tue, Jan 6, 2015 at 2:50 PM, William Stein wrote:
> On Tue, Jan 6, 2015 at 2:38 PM, Volker Braun wrote:
>> Do you have /scratch/wstein/sage-6.5.beta5/src/setup.py? I just checked and
>> that is definitely in the tarball.
>
>
> Nope --
>
> /scratch/wstein/sage-6.5.beta5$ ls -lht
> /scratch/wste
>
> sage -t --long --warn-long 38.0 src/sage/interfaces/maxima.py # Timed out
>
>
I get this too, 10.7.
--
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
Its tricky to test for memory leaks... if you want to go ahead and remove
these tests (or add # not tested) then that would be fine with me. Really
doctests are only useful if they are reproducible.
On Wednesday, January 7, 2015 12:01:56 AM UTC+1, John H Palmieri wrote:
>
> If you mean the fail
If you mean the failure in singular/polynomial.pyx, it looks more like a
memory leak:
sage -t --long src/sage/libs/singular/polynomial.pyx
**
File "src/sage/libs/singular/polynomial.pyx", line 166, in
sage.libs.singular.polynomi
On Tue, Jan 6, 2015 at 2:38 PM, Volker Braun wrote:
> Do you have /scratch/wstein/sage-6.5.beta5/src/setup.py? I just checked and
> that is definitely in the tarball.
Nope --
/scratch/wstein/sage-6.5.beta5$ ls -lht
/scratch/wstein/sage-6.5.beta5/src/setup.py
ls: cannot access /scratch/wstein/sa
On Tuesday, January 6, 2015 11:38:37 PM UTC+1, Volker Braun wrote:
>
> In that case you don't get an empty list for the "packages that failed".
>
I meant to say: You do get an empty list, of course.
--
You received this message because you are subscribed to the Google Groups
"sage-release" gro
Is the first failure also in the maxima tty interface or elsewhere?
I'we seen some OSX pty handling bugs
in http://trac.sagemath.org/ticket/16474, so I'm not really surprised that
there are random failures on Apple machines.
On Tuesday, January 6, 2015 5:20:05 PM UTC+1, John H Palmieri wrote:
Do you have /scratch/wstein/sage-6.5.beta5/src/setup.py? I just checked and
that is definitely in the tarball.
The reason why it doesn't give a useful error message is that the build
system does some build steps outside of a "package", for example installing
the Sage library. In that case you d
Hi,
I tried to build on Ubuntu 14.04 (SageMathCloud) in the same place,
same account, same environment, same setup as usual, where
sage-6.5.beta[1-3] all built perfectly and passed all tests. However,
this time the build completely failed (with sage-6.5.beta5).
It FAILS with:
---
...
make[3]: `
I don't know if you need the whole thing, but here is the end of the
snippet from ptestlong.log:
sage: maxima.facts() ## line 664 ##
[]
sage: var('a') ## line 666 ##
a
sage: maxima('limit(x^a,x,0)') ## line 668 ##
sage: sig_on_count() ## line 675 ##
0
sage: maxima._eval_line('1+1;') ## line 729
This is a timeout, right? Can you run the test with --verbose and see where
it hangs?
On Tuesday, January 6, 2015 2:50:40 AM UTC+1, John H Palmieri wrote:
>
> On Monday, January 5, 2015 2:38:41 PM UTC-8, Volker Braun wrote:
>>
>> As usual, get the "develop" branch or download the self-contained
On Monday, January 5, 2015 5:50:40 PM UTC-8, John H Palmieri wrote:
>
> On Monday, January 5, 2015 2:38:41 PM UTC-8, Volker Braun wrote:
>>
>> As usual, get the "develop" branch or download the self-contained source
>> tarball from http://www.sagemath.org/download-latest.html
>>
>> On two OS X m
On Monday, January 5, 2015 2:38:41 PM UTC-8, Volker Braun wrote:
>
> As usual, get the "develop" branch or download the self-contained source
> tarball from http://www.sagemath.org/download-latest.html
>
> On two OS X machines, two of the same failures as in 6.4.beta3:
---
> scons: `install' is up to date.
> Updating Cython code
> Enabling Cython debugging support
> Finished Cythonizing, time: 5.34 seconds.
> Discovering Python source code
> Discovered Python source, time: 0.05 seconds.
> Cleaning up stale installed files
> - cleaning /Applications/sage
On Sun, 12 Oct 2014 15:52:36 Volker Braun wrote:
> Workaround:
>
> mkdir -p local/share/sage/ext/valgrind
> make
Yes got me through, build in progress now.
Francois
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group
On Sun, 12 Oct 2014 15:14:47 Anne Schilling wrote:
> Hi Volker,
>
> Thanks! I get the following problem though on MacOS 10.6.8
>
> ...
> [repl ] reading sources... [ 69%] sage/repl/display/util
> [repl ] reading sources... [ 76%] sage/repl/interpreter
> [dynamics ] reading sources... [ 70
Workaround:
mkdir -p local/share/sage/ext/valgrind
make
--
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
Hi Volker,
Thanks! I get the following problem though on MacOS 10.6.8
...
[repl ] reading sources... [ 69%] sage/repl/display/util
[repl ] reading sources... [ 76%] sage/repl/interpreter
[dynamics ] reading sources... [ 70%] sage/dynamics/interval_exchanges/iet
[polynomia] reading sources
22 matches
Mail list logo
