Re: [sage-devel] Re: Patchbot gets priority and status of a ticket totally wrong
Or even better sage -i http://sage.math.washington.edu/home/robertwb/patches/patchbot-2.1.spkg On Wed, Mar 5, 2014 at 8:40 AM, Nathann Cohen nathann.co...@gmail.com wrote: ~/sage ./sage -patchbot /home/ralf/sage/src/bin/sage: line 751: /home/ralf/sage/local/bin/patchbot/patchbot.py: No such file or directory this is 6.2.base3 sage -i patchbot Nathann -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Patchbot gets priority and status of a ticket totally wrong
Or even better sage -i http://sage.math.washington.edu/home/robertwb/patches/patchbot-2.1.spkg HMm O_o I just noticed that the current branch on the version of Sage on which I installed the patchbot is not trac/develop anymore but a patchbot-specific thing... Does that mean I can't work with a version of Sage on which I installed the patchbot ? :-/ Nathann -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Patchbot gets priority and status of a ticket totally wrong
You can override the base_repo and base_branch field in your config to point to whatever upstream repository you want to track, see http://wiki.sagemath.org/buildbot/details. On Thu, Mar 6, 2014 at 2:04 AM, Nathann Cohen nathann.co...@gmail.com wrote: Or even better sage -i http://sage.math.washington.edu/home/robertwb/patches/patchbot-2.1.spkg HMm O_o I just noticed that the current branch on the version of Sage on which I installed the patchbot is not trac/develop anymore but a patchbot-specific thing... Does that mean I can't work with a version of Sage on which I installed the patchbot ? :-/ Nathann -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Patchbot gets priority and status of a ticket totally wrong
On Mon, Mar 3, 2014 at 2:45 AM, Frédéric Chapoton fchapot...@gmail.com wrote:
Hello,
it seems that the patchbot has not really digested the git transition.
I converted it to use the new git format, which is even better as it
now knows exactly what to test and can even do spkgs, and
non-sage-lib patches.
Of course the patchbot relies on people actually volunteering their
compute resources to run the patchbot, just take build a copy of sage
and run ./sage -patchbot and it'll start testing tickets. Maybe we
should manage a standard patchbot as well, though it's nice to have
coverage for many different platforms.
I
would be happy to see it back, as it was very useful in the development
process in the mercurial era.
To modify the patchbot, you have to clone from here
https://github.com/robertwb/sage-patchbot
and then propose a merge at the same place.
+1, changes welcome.
As for this snafu, the issue was that the description had tabs in it
which messed with the tab delimited format the patch uses to query the
ticket.
http://trac.sagemath.org/ticket/15759?format=tab
Le lundi 24 février 2014 14:12:27 UTC+1, Simon King a écrit :
Hi!
Clicking at the blob of #15759 (hence,
http://patchbot.sagemath.org/ticket/15759/), I notice that the patchbot
lists def f(self): in the status field, and even worse lists
... sage: instance = Foo() sage: Foo.f(instance) is instance.f() sage:
Foo.__dict__['f'](instance) is instance(f) }}} This makes them
compatible with, e.g., deprecated_function_alias: {{{ class Foo:
@cached_method def f(self): ... bar = deprecated_function_alias(12963,
f) }}}
in the priority field.
It has resolution: major and patches: 1., component:
positive_review,
git_branch: Simon King, milestone: enhancement.
All a bit odd. The corresponding information is correct on the ticket,
but not on the patchbot page.
I guess it needs fix, but I have no idea how to fix the patchbot.
Best regards,
Simon
--
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 to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Patchbot gets priority and status of a ticket totally wrong
Y ! Of course the patchbot relies on people actually volunteering their compute resources to run the patchbot, just take build a copy of sage and run ./sage -patchbot and it'll start testing tickets. H I did not know that O_O;;; I may not have been paying much attention, but still, I did not know that. I just started the patchbot on my office's computer. Would it make sense to send a message to sage-devel entitled The patchbot feeds on CPU, give it yours ! ? Nathann -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Patchbot gets priority and status of a ticket totally wrong
On Wednesday, March 5, 2014 10:22:05 AM UTC+1, Robert Bradshaw wrote: compute resources to run the patchbot, just take build a copy of sage and run ./sage -patchbot and it'll start testing tickets. ~/sage ./sage -patchbot /home/ralf/sage/src/bin/sage: line 751: /home/ralf/sage/local/bin/patchbot/patchbot.py: No such file or directory this is 6.2.base3 -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Patchbot gets priority and status of a ticket totally wrong
~/sage ./sage -patchbot /home/ralf/sage/src/bin/sage: line 751: /home/ralf/sage/local/bin/patchbot/patchbot.py: No such file or directory this is 6.2.base3 sage -i patchbot Nathann -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Patchbot gets priority and status of a ticket totally wrong
On Mon, Mar 3, 2014 at 3:04 AM, Volker Braun vbraun.n...@gmail.com wrote: There was some attempt to replace it with Jenkins at SD56, but I don't know how how far that progressed. Since the changeset information is now easily accessible through git it would make sense to replace it with a more run-of-the-mill continuous integration tool. Yes, I was looking into that, but it didn't seem quite like the tool for the job. I was going to take a look at how one by configure buildbot to perform patchbot-like duties, but school started and my studies took over all my time. -- Andrew -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: Patchbot gets priority and status of a ticket totally wrong
Hello,
it seems that the patchbot has not really digested the git transition. I
would be happy to see it back, as it was very useful in the development
process in the mercurial era.
To modify the patchbot, you have to clone from here
https://github.com/robertwb/sage-patchbot
and then propose a merge at the same place.
Frederic
Le lundi 24 février 2014 14:12:27 UTC+1, Simon King a écrit :
Hi!
Clicking at the blob of #15759 (hence,
http://patchbot.sagemath.org/ticket/15759/), I notice that the patchbot
lists def f(self): in the status field, and even worse lists
... sage: instance = Foo() sage: Foo.f(instance) is instance.f() sage:
Foo.__dict__['f'](instance) is instance(f) }}} This makes them
compatible with, e.g., deprecated_function_alias: {{{ class Foo:
@cached_method def f(self): ... bar = deprecated_function_alias(12963,
f) }}}
in the priority field.
It has resolution: major and patches: 1., component:
positive_review,
git_branch: Simon King, milestone: enhancement.
All a bit odd. The corresponding information is correct on the ticket,
but not on the patchbot page.
I guess it needs fix, but I have no idea how to fix the patchbot.
Best regards,
Simon
--
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 to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: Patchbot gets priority and status of a ticket totally wrong
There was some attempt to replace it with Jenkins at SD56, but I don't know
how how far that progressed. Since the changeset information is now easily
accessible through git it would make sense to replace it with a more
run-of-the-mill continuous integration tool.
On Monday, March 3, 2014 10:45:31 AM UTC, Frédéric Chapoton wrote:
Hello,
it seems that the patchbot has not really digested the git transition. I
would be happy to see it back, as it was very useful in the development
process in the mercurial era.
To modify the patchbot, you have to clone from here
https://github.com/robertwb/sage-patchbot
and then propose a merge at the same place.
Frederic
Le lundi 24 février 2014 14:12:27 UTC+1, Simon King a écrit :
Hi!
Clicking at the blob of #15759 (hence,
http://patchbot.sagemath.org/ticket/15759/), I notice that the patchbot
lists def f(self): in the status field, and even worse lists
... sage: instance = Foo() sage: Foo.f(instance) is instance.f() sage:
Foo.__dict__['f'](instance) is instance(f) }}} This makes them
compatible with, e.g., deprecated_function_alias: {{{ class Foo:
@cached_method def f(self): ... bar = deprecated_function_alias(12963,
f) }}}
in the priority field.
It has resolution: major and patches: 1., component:
positive_review,
git_branch: Simon King, milestone: enhancement.
All a bit odd. The corresponding information is correct on the ticket,
but not on the patchbot page.
I guess it needs fix, but I have no idea how to fix the patchbot.
Best regards,
Simon
--
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 to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
