Maybe it was caused by some temporary slowness of trac ?
Anyway, I have created #16872 to upgrade the patchbot to the latest
version. http://trac.sagemath.org/ticket/16872
Le vendredi 22 août 2014 12:17:21 UTC+2, Jeroen Demeyer a écrit :
Hello,
Given the message asking for patchbot
For the record, I found out how you end up with the U+200B, this always
happens when you paste a url from a trac page with chrome. For example, the
sage trac homepage has
Your trac account also grants you access to a class=ext-link
href=http://wiki.sagemath.org;span class=icon/spanthe sage
On Friday, July 26, 2013 7:54:41 PM UTC+1, Robert Bradshaw wrote:
On Fri, Jul 26, 2013 at 3:19 AM, David Loeffler
d.a.lo...@warwick.ac.uk javascript: wrote:
Hi Robert,
That's excellent -- thanks! One question: there are some tickets (e.g.
#14366) where it is not picking up
This was due to the trac change. I've updated the patchbot to
understand the this (and it's actually much cleaner as there are
csv/tsv formats now so I don't have to parse the html). It'll take a
while to actually update all the tickets in question.
On Thu, Jul 25, 2013 at 2:32 AM, David Loeffler
Hi Robert,
That's excellent -- thanks! One question: there are some tickets (e.g.
#14366) where it is not picking up correctly information in the ticket
comments specifying which patches to apply. Is it possible that this
part of the patchbot's code has also been broken by the trac update?
(I
On Fri, Jul 26, 2013 at 3:19 AM, David Loeffler
d.a.loeff...@warwick.ac.uk wrote:
Hi Robert,
That's excellent -- thanks! One question: there are some tickets (e.g.
#14366) where it is not picking up correctly information in the ticket
comments specifying which patches to apply. Is it possible
Some further data: the problem is definitely with the patchbot server
process running at patchbot.sagemath.org -- if you request a list of all
tickets with
http://patchbot.sagemath.org/ticket/?status=allorder=idrawpretty
then it really does return all tickets, but for the majority of them, it
