On Saturday, May 17, 2014 11:42:43 AM UTC+2, Ralf Stephan wrote:
>
> It is possible that the /tmp installation is broken anyway. With
> setuptools-3.6
> I get 4 out of 4 failures because some paths point back to the original
> sage/
> directory, but some not and the underlying files are not there
On Saturday, May 17, 2014 11:42:43 AM UTC+2, Ralf Stephan wrote:
>
> It is possible that the /tmp installation is broken anyway. With
> setuptools-3.6
> I get 4 out of 4 failures because some paths point back to the original
> sage/
> directory, but some not and the underlying files are not the
On Thu, May 15, 2014 at 12:53 AM, Ralf Stephan wrote:
> It may be possible to test newer package versions in patchbot without
> official ticket by forking Sage on github, installing the package in the
> local
> Sage, publish the changed branch on github, and use that branch as
> base_repo with pat
It is possible that the /tmp installation is broken anyway. With
setuptools-3.6
I get 4 out of 4 failures because some paths point back to the original
sage/
directory, but some not and the underlying files are not there (numpy for
example).
Moreover, none of the 6.2 TestsPassed runs (n=47) is a
It would be great if that worked. I disabled the tmp directory for the
moment and am testing all tickets in the same directory, but that can leave
the tree in a bad state.
Peter
Op vrijdag 16 mei 2014 10:03:01 UTC+1 schreef Ralf Stephan:
>
> Ah I finally found the relevant upstream ticket:
>
Ah I finally found the relevant upstream ticket:
https://bitbucket.org/pypa/setuptools/issue/168/ez_setuppy-failing-sporadically-when
which appears resolved with setuptools-3.5.2
Next is testing of a version >= 3.5.2
Regards,
On Thursday, May 15, 2014 9:53:36 AM UTC+2, Ralf Stephan wrote:
>
> It
It may be possible to test newer package versions in patchbot without
official ticket by forking Sage on github, installing the package in the
local
Sage, publish the changed branch on github, and use that branch as
base_repo with patchbot. This may work also with unsafe tickets because
the clonin
http://trac.sagemath.org/ticket/16350
Please review.
Regards,
On Tuesday, May 13, 2014 9:51:17 PM UTC+2, Peter Bruin wrote:
>
> I started a patchbot based on 6.3.beta1, and the problem has unfortunately
> popped up again with the new setuptools version:
>
>
> http://patchbot.sagemath.org/log/16
I started a patchbot based on 6.3.beta1, and the problem has unfortunately
popped up again with the new setuptools version:
http://patchbot.sagemath.org/log/16348/debian/wheezy/sid/x86_64/3.2.0-57-generic/selmer/2014-05-13%2019:57:47%20+0100
Op woensdag 7 mei 2014 10:05:32 UTC+1 schreef Ralf St
https://github.com/robertwb/sage-patchbot/pull/24
and if you change patchbot/trac.py:pull_from_trac() in line 309
such that after
if not inplace_safe():
an exception is raised (e.g. just "raise") then patchbot will only
checkout and test tickets in-place, i.e. no reinstall. Unsafe ticket
OK, I see, this has now happened to my patchbot on #15316.
Op woensdag 7 mei 2014 17:18:17 UTC+1 schreef Ralf Stephan:
>
> On Wed, May 7, 2014 at 5:08 PM, Peter Bruin
> > wrote:
>
>> Oh yes you're right. Making it the base branch is necessary too.
>>>
>> Something that worked for me is making t
Ralf Stephan wrote:
On Wed, May 7, 2014 at 5:08 PM, Peter Bruin mailto:pjbr...@gmail.com>> wrote:
Oh yes you're right. Making it the base branch is necessary too.
Something that worked for me is making the changes without
committing them; then the patchbot won't undo those chang
On Wed, May 7, 2014 at 5:08 PM, Peter Bruin wrote:
> Oh yes you're right. Making it the base branch is necessary too.
>>
> Something that worked for me is making the changes without committing
> them; then the patchbot won't undo those changes.
>
That will work until a ticket with "unsafe" chang
>
> Oh yes you're right. Making it the base branch is necessary too.
>
Something that worked for me is making the changes without committing them;
then the patchbot won't undo those changes.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To uns
Oh well, so base_branch means remote base branch on github.
So, let's push that ticket.
On Wednesday, May 7, 2014 4:02:25 PM UTC+2, Ralf Stephan wrote:
>
> Oh yes you're right. Making it the base branch is necessary too.
>
--
You received this message because you are subscribed to the Google Gro
Oh yes you're right. Making it the base branch is necessary too.
--
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 sage-devel+unsubscr...@googlegroups.com.
To post t
OK, I'll try that after the patchbot finishes the current ticket (which
seems to be unaffected by the setuptools problem).
Op woensdag 7 mei 2014 11:27:19 UTC+1 schreef Ralf Stephan:
>
> Just change builds/pkg.../package-version, download to upstream, run sage
> to fix checksums, maybe also sag
Just change builds/pkg.../package-version, download to upstream, run sage
to fix checksums, maybe also sage -f setuptools, and then use that as base.
I had no problems in two runs after that but more data is needed.
This goes back as far as the first commit after 6.1.1
On 7 May 2014 12:04, "Peter
To try this one has to apply #16300 and then run patchbot with the
resulting branch as the base branch, is that correct?
Op woensdag 7 mei 2014 10:05:32 UTC+1 schreef Ralf Stephan:
>
> http://trac.sagemath.org/ticket/16300
>
> People running patchbot with errors on setuptools install please try
http://trac.sagemath.org/ticket/16300
People running patchbot with errors on setuptools install please try
version 2.2b1 of setuptools and report if this changes the behaviour
or not.
Regards,
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To u
This is not SMC specific. Also the CentOS machine running patchbot has
these build failures
occasionally.
http://patchbot.sagemath.org/log/8734/CentOS/6.5/x86_64/2.6.32-431.5.1.el6.x86_64/kepler.math.osu.edu/2014-04-30%2014:37:38%20-0400
On Monday, May 5, 2014 8:56:17 AM UTC+2, Ralf Stephan wrote
21 matches
Mail list logo
