Hi!
On 2015-04-21, Clemens Heuberger clemens.heuber...@aau.at wrote:
I have a somewhat related problem: Since February (I do not recall the exact
revision, but might very well be early in the 6.6 release cycle), I cannot do
a
parallel build with 4 processes on my notebook with 4 GB RAM
Hello Jeroen,
1) I am sorry for having released a broken patchbot without testing it. All
my apologies. As far as I know, 2.3.3 is now repaired.
2) the *only current working patchbot* seems to be pcl337b, running
patchbot 2.3.2 probably with --skip-base
All the other machines seem to meet
On Mon, 20 Apr 2015, Nathann Cohen wrote:
I made http://trac.sagemath.org/ticket/16865 from this 8 months ago,
but nobody has said which should be defined correct way.
Given the following output, it would indeed make more sense if 2 were... at the
top.
sage: Poset([[1,2],[[1,2]]]).top()
2
I just pushed an initial try. If you care, could you have a look whether
it's in principle OK?
Thanks,
Martin
--
You received this message because you are subscribed to the Google Groups
sage-combinat-devel group.
To unsubscribe from this group and stop receiving emails from it, send an
On 2015-04-21 15:09, Jeroen Demeyer wrote:
On 2015-04-21 10:00, Jean-Pierre Flori wrote:
That is put Cython directives for linking, including C files and so on,
at the top of the pyx file?
Please wait until I fix
http://trac.cython.org/ticket/845
I now have a pull request for this issue:
On 04/21/2015 11:35 AM, Thierry wrote:
could this mean that there is some issue with Cython compilation (e.g.
memory leak) ?
Not necessarily a leak, but Cython 0.22 sneaked into Sage 6.6.beta0, in
February. (Leaks usually just increase the amount of virtual memory
used, not the number of pages
On 04/21/2015 08:27 AM, Simon King wrote:
On 2015-04-21, Clemens Heuberger clemens.heuber...@aau.at wrote:
I have a somewhat related problem: Since February (I do not recall the exact
revision, but might very well be early in the 6.6 release cycle), I cannot
do a
parallel build with 4
I think that I currently have arando and sage4 running correctly with
the latest patchbot.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I think we should definitely have a raspbian buildbot. It is tricky because of
the hardware limitations, but it should be possible.
Another option is to run a virtual machine emulating a raspberry pi. I recently
compiled sage 6.5 in such a VM, an it took almost a week. I still have to build
a
On 2015-04-21 10:00, Jean-Pierre Flori wrote:
That is put Cython directives for linking, including C files and so on,
at the top of the pyx file?
Please wait until I fix
http://trac.cython.org/ticket/845
Then you will be able to write those library dependencies in the .pxd
files where they
On 04/21/2015 02:22 PM, Volker Braun wrote:
+1 to moving as much as possible into the individual pyx file and away
from a global module_list.py
Yes, planned since years, but we cannot handle e.g. OS-specific stuff
there, AFAIK.
Can't we test for underlinking using ldd / readelf on linux? I'm
Yo !
and so I don't yet even know where to look at.
I do not know either. I would add print 'hey' in the code to see what
gets executed.
Nathann
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop
Hi Frederic,
I can provide you an account on the arando box, so that you can have your
own instance of a really running patchbot.
How about that?
Dima
On Tuesday, 21 April 2015 07:15:13 UTC+1, Frédéric Chapoton wrote:
Hello Jeroen,
1) I am sorry for having released a broken patchbot without
Hi,
could this mean that there is some issue with Cython compilation (e.g.
memory leak) ?
Ciao,
Thierry
On Tue, Apr 21, 2015 at 10:24:07AM +0200, leif wrote:
On 04/21/2015 08:27 AM, Simon King wrote:
On 2015-04-21, Clemens Heuberger clemens.heuber...@aau.at wrote:
I have a somewhat
Dear all,
It seems we're shifting from the original way we were building Cython
extensions where each extension was listed in module_list.py to use
wildcards in module_list.py.
See #7987 and #15410 for wide coverage tickets, and e.g. #17767 for more
focused ones.
This is problematic when some
Okay, for the time being I am just excluding this ticket manually by adding
in extra line in get_ticket.
Am Dienstag, 21. April 2015 16:33:16 UTC+2 schrieb Frédéric Chapoton:
Or maybe it can, with something like
{bonus:{Bouillaguet:-1000}}
inside config.json
Frederic
Le mardi 21 avril
Another issue has come up. My patchbot seems to be fascinated by 15209 and
keeps retesting it, see http://patchbot.sagemath.org/ticket/15209/
Any suggestions?
Am Dienstag, 14. April 2015 16:15:00 UTC+2 schrieb Frédéric Chapoton:
Great ! I am happy every time I see a green blob !
In
Yes, I have seen that this morning. It loops because the Spkg do not make
true reports, so it thinks it has not done anything on that ticket. It only
happens because it does not find any better ticket to work on, I think.
I have modified the patchbot code to avoid that, changes will be in the
Or maybe it can, with something like
{bonus:{Bouillaguet:-1000}}
inside config.json
Frederic
Le mardi 21 avril 2015 16:24:08 UTC+2, Frédéric Chapoton a écrit :
Hmm, sorry, it seems that there is no clear way to skip a chosen ticket..
So the json config file will not help.
Le mardi 21
Hmm, sorry, it seems that there is no clear way to skip a chosen ticket..
So the json config file will not help.
Le mardi 21 avril 2015 16:15:41 UTC+2, Frédéric Chapoton a écrit :
Yes, I have seen that this morning. It loops because the Spkg do not make
true reports, so it thinks it has not
+1 to moving as much as possible into the individual pyx file and away from
a global module_list.py
Can't we test for underlinking using ldd / readelf on linux? I'm sure
somebody has written a solution for that. Documenting is nice, but testing
is better.
On Tuesday, April 21, 2015 at
Release of GCC 5.1 is scheduled for Wednesday, April 22nd.
I took the first release candidate and tried to build Sage 6.6 with it:
* MPIR fails in 'configure' -- easy to fix, see #18247
* Lcalc fails to build -- usual C++ issues, subset of those
with clang, easy to
It seems that Cython is now cythonizing multiple files in a single process,
that is, the Cython process does not quit while cythonizing the entire Sage
library. Combined with a small memory leak in Cython means that you
currently need about 5gb of ram.
For example, in the attached plot I
On 04/22/2015 05:01 AM, Volker Braun wrote:
It seems that Cython is now cythonizing multiple files in a single
process, that is, the Cython process does not quit while cythonizing the
entire Sage library. Combined with a small memory leak in Cython means
that you currently need about 5gb of
--skip-base only disables the initial run (which is useful for
preventing a rogue/broken install from declaring all tickets as
broken).
On Tue, Apr 14, 2015 at 2:49 AM, Jan Keitel jocalareanetw...@gmail.com wrote:
Whatever the problem was before, it is gone now - at least it just
successfully
Here is the tail of the typical terminal output:
...
warning: sage/rings/finite_rings/element_givaro.pyx:1105:39: local variable
'r' referenced before assignment
warning: sage/rings/finite_rings/element_givaro.pyx:1120:50: local variable
'r' referenced before assignment
warning:
26 matches
Mail list logo
