On Sunday, November 22, 2015, Mark Bell wrote:
> Thank you for tracking this down so quickly and for already submitting a
> correction. If I am understanding your response correctly then I think I
> need to just hope that trac 14243 is accepted and then wait for the next
> version of sage that in
Volker just released 6.10.beta5. I think if any one else
is interested in getting these in sage 6.10, this would be
a good time to review the tickets. After that we may be looking
at (6.10)++ whatever that is.
Francois
On 11/11/15 13:32, François Bissey wrote:
Hi all,
I have put three tickets
> Its a Jenkins installation, whereas we use buildbot. From a quick glance its
> not clear to me whether it can be used to run independent VMs that integrate
> into our buildbot master. Also, what kind of resources can they provide? The
> Sage testsuite is huge, slow, and guzzles memory.
Those are
Its a Jenkins installation, whereas we use buildbot. From a quick glance
its not clear to me whether it can be used to run independent VMs that
integrate into our buildbot master. Also, what kind of resources can they
provide? The Sage testsuite is huge, slow, and guzzles memory.
On Sunday, N
> Whats IMHO preventing us from better testing is container support, right now
> the testsuite fails inside docker. Using containers, the patchbot could
> snapshot clean builds and test on top of that. And automatically test
> third-party packages.
>
> More machines for the buildbot would also be g
