Re: [sage-devel] --patchbot

Hi, Thank you for the information, both of these work: https://trac.sagemath.org/wiki/patchbot https://wiki.sagemath.org/buildbot?action=info Regards, phiho On Mon, May 30, 2022 at 2:53 PM Samuel Lelievre wrote: > phiho wrote: > > > > Is this link correct: https://wiki.sagemath.org/buildbo

Re: [sage-devel] --patchbot

phiho wrote: > > Is this link correct: https://wiki.sagemath.org/buildbot ? Clicking on "Info" at the top gives the history of the page, even for a deleted page. https://wiki.sagemath.org/buildbot?action=info -- You received this message because you are subscribed to the Google Groups "sage-de

Re: [sage-devel] --patchbot

I guess this is https://wiki.sagemath.org/patchbot which has moved to https://trac.sagemath.org/wiki/patchbot Le 30/05/2022 à 14:37, ph h a écrit : Dear All, Is this link correct: https://wiki.sagemath.org/buildbot ? *This page does not exist yet. You can create a new empty page, or use one

[sage-devel] --patchbot

Dear All, Is this link correct: https://wiki.sagemath.org/buildbot ? *This page does not exist yet. You can create a new empty page, or use one of the page templates.* Thank you for your help. phiho ~/sage-9.7/b1.3$ root.beta1 -patchbot Traceback (most recent call last): File "", line 1, in

Re: [sage-devel] Patchbot on GitHub Actions

On Sat, 5 Feb 2022, 18:21 Matthias Koeppe, wrote: > It is now possible to run the Sage Patchbot in a container on GitHub > Actions. > > Go to https://github.com/sagemath/sage-patchbot, use the Fork button to > create a fork in your account. > > Go to the Actions tab, select "Run patchbot". Push

[sage-devel] Patchbot on GitHub Actions

It is now possible to run the Sage Patchbot in a container on GitHub Actions. Go to https://github.com/sagemath/sage-patchbot, use the Fork button to create a fork in your account. Go to the Actions tab, select "Run patchbot". Push "Run workflow". Instead of the default platform, ubuntu-focal-

Re: [sage-devel] Patchbot/CI improvements

Thanks, I've opened - https://github.com/sagemath/sage-patchbot/issues/148 - https://github.com/sagemath/sage-patchbot/issues/149 On Sunday, January 23, 2022 at 11:57:02 AM UTC-8 vdelecroix wrote: > Le 23/01/2022 à 18:35, Matthias Koeppe a écrit : > > Patchbot experts: > > 1) Currently the patch

Re: [sage-devel] Patchbot/CI improvements

Le 23/01/2022 à 18:35, Matthias Koeppe a écrit : Patchbot experts: 1) Currently the patchbot does not run on certain tickets that make changes to build/pkgs, so we do not have automatic testing for these tickets. Is this something that can be changed? I would say that this is doable (since if I

[sage-devel] Patchbot/CI improvements

Patchbot experts: 1) Currently the patchbot does not run on certain tickets that make changes to build/pkgs, so we do not have automatic testing for these tickets. Is this something that can be changed? 2) Can "make doc-pdf" please be added? I don't know if Volker's integration scripts look at

[sage-devel] patchbot owners, please update to 3.0.3

Hello, github has removed the git: protocol. So patchbots need to be updated. please update your patchbot to the latest available tag Frédéric -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails

[sage-devel] patchbot trouble

Unfortunately, I keep getting a strange test failure in my patchbot install. When run alone, the test passes. It only occurs when executing LANG=C.UTF-8 python3 -m sage_patchbot.patchbot --config=config.json martin@convex63:~/sage-patchbot$ cat config.json { "parallelism": 4, "sage_ro

[sage-devel] patchbot owners, please upgrade

to the latest patchbot version, namely 3.0.2 Among other details, this handles better multi-line lazy-imports. Frederic https://github.com/sagemath/sage-patchbot/releases -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

[sage-devel] Patchbot r640 fails with "disk full"

Patchbot r640 seems to be failing for lack of disk space: https://trac.sagemath.org/ticket/30230#comment:14 -- 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 s

[sage-devel] patchbot security

Hi, I'm wondering what safety measures are taken for distributing code to the patchbot clients. E.g. if I where to register a new github account and create a ticket that uploads all files from the user to a server of my choice (maybe via a malicous doctest), is that ticket still going to be di

[sage-devel] patchbot server down

https://patchbot.sagemath.org/ displays an Internal Server Error -- 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

Re: [sage-devel] patchbot questions

On 24.04.19 22:16, John H Palmieri wrote: > > > On Tuesday, April 23, 2019 at 12:18:13 AM UTC-7, Daniel Krenn wrote: > > On 23.04.19 01:37, John H Palmieri wrote: > > I was running a patchbot successfully until some time last week. For > > reasons I don't understand, I did "git pull"

Re: [sage-devel] patchbot questions

On Tuesday, April 23, 2019 at 12:18:13 AM UTC-7, Daniel Krenn wrote: > > On 23.04.19 01:37, John H Palmieri wrote: > > I was running a patchbot successfully until some time last week. For > > reasons I don't understand, I did "git pull" on the patchbot, and now it > > won't run with Python 2,

Re: [sage-devel] patchbot questions

On 23.04.19 01:37, John H Palmieri wrote: > I was running a patchbot successfully until some time last week. For > reasons I don't understand, I did "git pull" on the patchbot, and now it > won't run with Python 2, complaining AFAIK, the patchbot runs on Python 3 only (so, yes, you need this insta

[sage-devel] patchbot questions

I was running a patchbot successfully until some time last week. For reasons I don't understand, I did "git pull" on the patchbot, and now it won't run with Python 2, complaining File "sage_patchbot/plugins.py", line 309 yield from names ^ SyntaxError: invalid syntax Do I ne

[sage-devel] Patchbot steenrod troubles

However is in charge of it, take a look... -- 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 em

[sage-devel] Patchbot zancara: Disk quota exceeded

There are problems with patchbot zancara: OSError: [Errno 122] Disk quota exceeded: '/home/mi/kliem/.sage/temp/zancara/16740' Full log: https://patchbot.sagemath.org/log/27152/debian/9.6/x86_64/4.9.0-8-amd64/zancara/2019-01-29%2021:56:24 -- You received this message because you are subscrib

Re: [sage-devel] Patchbot trouble with flint/fmpz.h

On 20 June 2018 at 09:23, Erik Bray wrote: > On Tue, Jun 19, 2018 at 5:13 PM Jeroen Demeyer wrote: > > > > Several patchbots are showing this error: > > > > [eclib-20171002.p0] libtool: compile: g++ -std=gnu++11 > > -DPACKAGE_NAME=\"eclib\" -DPACKAGE_TARNAME=\"eclib\" > > -DPACKAGE_VERSION=\"20

Re: [sage-devel] Patchbot trouble with flint/fmpz.h

On Tue, Jun 19, 2018 at 5:13 PM Jeroen Demeyer wrote: > > Several patchbots are showing this error: > > [eclib-20171002.p0] libtool: compile: g++ -std=gnu++11 > -DPACKAGE_NAME=\"eclib\" -DPACKAGE_TARNAME=\"eclib\" > -DPACKAGE_VERSION=\"20171002\" "-DPACKAGE_STRING=\"eclib 20171002\"" > -DPACKAGE_

[sage-devel] Patchbot trouble with flint/fmpz.h

Several patchbots are showing this error: [eclib-20171002.p0] libtool: compile: g++ -std=gnu++11 -DPACKAGE_NAME=\"eclib\" -DPACKAGE_TARNAME=\"eclib\" -DPACKAGE_VERSION=\"20171002\" "-DPACKAGE_STRING=\"eclib 20171002\"" -DPACKAGE_BUGREPORT=\"john.crem...@gmail.com\" -DPACKAGE_URL=\"\" -DPACKA

[sage-devel] patchbot problems

Hi all, I noticed this morning that the patchbot was returning error 500s upon listing open tickets. I realized after some investigation that this was due to a virtual memory limit of 1 GB on the server's worker processes that was being surpassed on these requests*. For now I've doubled that lim

Re: [sage-devel] Patchbot and its trust issues

My fault. I should not have upgraded the server. New release is patchbot tagged 2.7.1. Please clients, update. Le jeudi 23 novembre 2017 18:43:43 UTC+1, Thierry (sage-googlesucks@xxx) a écrit : > > Hi, > > if you update the patchbot server to not send the list of trusted authors > anymore, pl

Re: [sage-devel] Patchbot and its trust issues

Hi, if you update the patchbot server to not send the list of trusted authors anymore, please first provide an adapted version of the client (and imho, continue to serve the file until all active clients get up-to-date) ! I got: [2017-11-23 15:35:10] Getting trusted author list... [2017-11-23 15

Re: [sage-devel] Patchbot and its trust issues

On 16/11/2017 11:32, Erik Bray wrote: On Wed, Nov 15, 2017 at 10:00 AM, David Loeffler wrote: I'd like to request opinions on whether we should get rid of the "Trusted Authors" check in the Sage patchbot. At present, the patchbot won't test a ticket unless all of the names in the Trac "Authors

Re: [sage-devel] Patchbot and its trust issues

On Wed, Nov 15, 2017 at 10:00 AM, David Loeffler wrote: > I'd like to request opinions on whether we should get rid of the "Trusted > Authors" check in the Sage patchbot. > > At present, the patchbot won't test a ticket unless all of the names in the > Trac "Authors" field have had at least one ti

[sage-devel] Patchbot and its trust issues

I'd like to request opinions on whether we should get rid of the "Trusted Authors" check in the Sage patchbot. At present, the patchbot won't test a ticket unless all of the names in the Trac "Authors" field have had at least one ticket previously merged. Presumably the intention of this is to pre

[sage-devel] patchbot server down

https://patchbot.sagemath.org/ gives an Internal Server Error right now. Some pages work, such as the build pages for individual tickets, but others are just screaming. I'll look into it. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubs

Re: [sage-devel] Patchbot failures metaticket

On Tuesday, 12 September 2017 18:43:00 UTC+2, vdelecroix wrote: > > Hi Marteen, > > Though in an ideal world > - tickets should not be merged if any patchbot is not happy with it > Hi looked a bit more into this stuff and I think that the main reason why this happens is that even though we

Re: [sage-devel] Patchbot failures metaticket

Hi Vincent, Thanks for pointing out the point of view from a patchbot maintainer, my statement "I think a complete burden is highly exaggerated" was made from my perspective as a developer not knowing how this looks from a patchbot maintainer point of view. And I can see that having to deal wit

Re: [sage-devel] Patchbot failures metaticket

Hi Marteen, "complete burden" = "each release". So precisely, we need somebody to volunteer to maintain this list. I already hardly find the energy to fill a ticket for the reasons why my patchbot is not working any more at each new release (including the fact that I need to search for a reas

Re: [sage-devel] Patchbot failures metaticket

Hi Vincent, I think "a complete burden" is highly exaggerated, there should not be a new patchbot ticket to often. And if someone has to create a ticket then just copy pasting the failing files and the ticket number to the ticket description should not be to much work. As for removing old stuf

Re: [sage-devel] Patchbot failures metaticket

Hi, I think a meta-ticket is a complete burden to maintain. And as already said in other mails, this identification should be done by other means. Vincent On 11/09/2017 18:59, Maarten Derickx wrote: Hi all, During the recent writing of new code and reviewing I got annoyed that it costs real

Re: [sage-devel] Patchbot failures metaticket

On 12/09/2017 12:23, Jeroen Demeyer wrote: On 2017-09-11 18:59, Maarten Derickx wrote: I think that all patchbot failure tickets should automatically deserve the status critical. They should be blockers (unless the error comes from a broken patchbot). +1 p.s. Tips on how to search for tick

Re: [sage-devel] Patchbot failures metaticket

On 2017-09-11 18:59, Maarten Derickx wrote: I think that all patchbot failure tickets should automatically deserve the status critical. They should be blockers (unless the error comes from a broken patchbot). p.s. Tips on how to search for tickets on trac are welcome! Google site:trac.sage

Re: [sage-devel] Patchbot failures metaticket

On Mon, Sep 11, 2017 at 12:59 PM, Maarten Derickx < m.derickx.stud...@gmail.com> wrote: > Hi all, > > During the recent writing of new code and reviewing I got annoyed that it > costs really a lot of effort for me to see if there was already a ticket > for a certain patchbot failure. I therefore d

[sage-devel] Patchbot failures metaticket

Hi all, During the recent writing of new code and reviewing I got annoyed that it costs really a lot of effort for me to see if there was already a ticket for a certain patchbot failure. I therefore decided to create a metaticket that should serve as an overview of all currently known patchbot

[sage-devel] Patchbot raises error but status is still shown as pending.

Hi, At https://patchbot.sagemath.org/ticket/23610/ you can see that the patchbot status of two different patchbots is mentioned as pending in all the tests listed on that page. However if you look at one of the logs

[sage-devel] Patchbot monitoring

Does anyone who runs / administers Sage patchbots have any hints/tips regarding monitoring of their patchbots? In particular there are two types of things I'd like to monitor: 1. General health status of the patchbot--is it up and running and how many unique tickets has it tested, etc. Are the t

[sage-devel] patchbot server is off today

Due to maintenance of our infrastructure, the patchbot server is not available today. This will impact all trac pages (trying to load the patchbot icons). And of course, the patchbot clients will not be able to send their reports to the patchbot server. This should come back at 19 (French loca

[sage-devel] patchbot breeders please update to 2.6.8

To people that run patchbots (thank you for that) I would like to suggest to update to patchbot 2.6.8. Some are still running 2.6.4 or 2.6.6, and there have been some real enhancements since, for example better plugins and trying harder not to test closed tickets. Frederic -- You received th

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

On Mon, Feb 20, 2017 at 04:32:32AM -0800, Volker Braun wrote: > There is no general client request body size limit, this is a configuration > setting for your wsgi server or reverse proxy that is in front of the > patchbot. If you need help debugging this then post the relevant **server** > log

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

There is no general client request body size limit, this is a configuration setting for your wsgi server or reverse proxy that is in front of the patchbot. If you need help debugging this then post the relevant **server** log that shows the 413 being triggered. On Thursday, January 26, 2017 a

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

On 2017-02-20 08:48, Thierry wrote: Hi, On Mon, Feb 20, 2017 at 08:32:18AM +0100, Jeroen Demeyer wrote: On 2017-01-26 10:18, Daniel Krenn wrote: Starting a patchbot results in the error below. Any ideas? This issue makes it *impossible* for me to run a patchbot. If anybody is able to fix th

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

Hi, On Mon, Feb 20, 2017 at 08:32:18AM +0100, Jeroen Demeyer wrote: > On 2017-01-26 10:18, Daniel Krenn wrote: > >Starting a patchbot results in the error below. Any ideas? > > This issue makes it *impossible* for me to run a patchbot. > > If anybody is able to fix this, please do so. What happ

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

On 2017-01-26 10:18, Daniel Krenn wrote: Starting a patchbot results in the error below. Any ideas? This issue makes it *impossible* for me to run a patchbot. If anybody is able to fix this, please do so. -- You received this message because you are subscribed to the Google Groups "sage-deve

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

On 2017-01-26 10:40, Thierry wrote: > the patchbot server is regularly maintained and seems healthy (i just > rebooted it to be sure that the issue does not come from that side). > Apparently, the reason is that your patchbot client sends a log that is > too big. I already met that issue once, the

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

Hi, the patchbot server is regularly maintained and seems healthy (i just rebooted it to be sure that the issue does not come from that side). Apparently, the reason is that your patchbot client sends a log that is too big. I already met that issue once, the reason was that i ran a client on a fre

[sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

Starting a patchbot results in the error below. Any ideas? ... [2017-01-26 09:15:56] #0: init phase REPORT {'base': '7.6.beta1', 'deps': [], 'git_base': 'ac31f23ba52013c7aa6cc83660c50bfe9aab952a', 'git_base_human': '7.6.beta1', 'git_branch': 'develop', 'git_commit': 'ac31f23ba52013c7aa6cc8366

Re: [sage-devel] patchbot: ticket list latency?

On 2017-01-05 16:00, Clemens Heuberger wrote: I am playing around with a patchbot and I am wondering whether there is some kind of caching or other latency involved with the tickets which are available for testing. I am wondering that too. It has happened in the past that the patchbots were te

[sage-devel] patchbot: ticket list latency?

I am playing around with a patchbot and I am wondering whether there is some kind of caching or other latency involved with the tickets which are available for testing. For instance, ticket #21992: the branch was last changed 25 hours ago; 6 hours ago it was set to positive review. However,

Re: [sage-devel] patchbot quasar timeouts and coverage-plugin

quasar might timeout (and not the others) because it is installed with a lot of optional packages (basically all minus the one that cause trouble). The relevant optional tests might be, I will test later on sage: g = graphs.LocalMcLaughlinGraph(); g Local McLaughlin Graph: Graph on 162 vertices

[sage-devel] patchbot quasar timeouts and coverage-plugin

On at least two tickets I found TestsFailed 7.5.rc0 Ubuntu/16.04/x86_64/4.4.0-53-generic/quasar because of timeouts. At https://trac.sagemath.org/ticket/22064: sage -t --long src/sage/graphs/generators/smallgraphs.py # Timed out At https://trac.sagemath.org/ticket/21968: sage -t --long src/sag

Re: [sage-devel] patchbot Internal Server Error

Le vendredi 7 octobre 2016 13:29:55 UTC+2, Thierry (sage-googlesucks@xxx) a écrit : > > Hi, > > the log acknowledged an error, but it was very unclear, i relaunched the > services and it seems to work now. > > Thank you Thierry! Eric. -- You received this message because you are subscribed

Re: [sage-devel] patchbot Internal Server Error

Hi, the log acknowledged an error, but it was very unclear, i relaunched the services and it seems to work now. Ciao, Thierry On Fri, Oct 07, 2016 at 12:51:11AM -0700, Eric Gourgoulhon wrote: > Hi, > > Since yesterday, whenever I try to read some patchbot report about a > ticket, I'm getting

[sage-devel] patchbot Internal Server Error

Hi, Since yesterday, whenever I try to read some patchbot report about a ticket, I'm getting the message Internal Server Error from https://patchbot.sagemath.org/ Is it only me ? Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubs

Re: [sage-devel] patchbot sage4 fails with permission denied

On 2016-09-09 10:20, Daniel Krenn wrote: On #21204 (with 7.4.beta3) as well as on #21205 (with 7.4.beta4) patchbot Gentoo Base System/2.2/x86_64/3.2.1-gentoo-r2/sage4 fails building with [widgetsnbextension-1.2.6] OSError: [Errno 13] Permission denied: '/home/worker/.jupyter' This is h

[sage-devel] patchbot sage4 fails with permission denied

On #21204 (with 7.4.beta3) as well as on #21205 (with 7.4.beta4) patchbot Gentoo Base System/2.2/x86_64/3.2.1-gentoo-r2/sage4 fails building with [widgetsnbextension-1.2.6] OSError: [Errno 13] Permission denied: '/home/worker/.jupyter' -- You received this message because you are subscribed

Re: [sage-devel] Patchbot tmonteil-debian-jessie-32 has "No space left on device"

Hi, i noticed that one hour ago after Frederic told me there was an issue, i relaunched the patchbot after some cleanup. Thanks for the reporting anyway ! Ciao, Thierry On Wed, Aug 31, 2016 at 10:57:17AM +0200, Jeroen Demeyer wrote: > The patchbot tmonteil-debian-jessie-32 is spamming all tic

[sage-devel] Patchbot tmonteil-debian-jessie-32 has "No space left on device"

The patchbot tmonteil-debian-jessie-32 is spamming all tickets as BuildFailed because of "No space left on device". See for example https://patchbot.sagemath.org/log/21126/debian/8.3/i686/3.16.0-4-586/tmonteil-debian-jessie-32/2016-08-31%2001:20:27?short -- You received this message because y

Re: [sage-devel] patchbot server refuses to connect

OK, leaving it as -- not rebooting. On Tue, Aug 9, 2016 at 12:51 AM, Frédéric Chapoton wrote: > Please do not reboot. We are currently doing an rsync for the database, > and we decided to turn the server off for a moment. > > Thierry Monteil is doing the job. Maybe he can tell us about the stat

Re: [sage-devel] patchbot server refuses to connect

Please do not reboot. We are currently doing an rsync for the database, and we decided to turn the server off for a moment. Thierry Monteil is doing the job. Maybe he can tell us about the status ? Le mardi 9 août 2016 08:18:25 UTC+2, William a écrit : > > On Mon, Aug 8, 2016 at 10:11 PM, Ralf

Re: [sage-devel] patchbot server refuses to connect

Thanks. I always try to help with such things but mostly lose because I'm lacking server admin skills. On Tue, Aug 9, 2016 at 8:18 AM William Stein wrote: > On Mon, Aug 8, 2016 at 10:11 PM, Ralf Stephan wrote: > > It is pingable however. > > I can try to reboot the computer again, maybe. As be

Re: [sage-devel] patchbot server refuses to connect

On Mon, Aug 8, 2016 at 10:11 PM, Ralf Stephan wrote: > It is pingable however. I can try to reboot the computer again, maybe. As before, I'm not even sure which computer it's hosted on, and frankly I don't even want to touch it unless somebody will very clearly volunteer to immediately migrate i

[sage-devel] patchbot server refuses to connect

It is pingable however. -- 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@go

Re: [sage-devel] patchbot server not responding

Please check up on fileserver.sagemath.org, too, while you are at it... On Thursday, July 21, 2016 at 2:20:17 AM UTC+2, William wrote: > > On Wed, Jul 20, 2016 at 12:39 PM, Frédéric Chapoton > > wrote: > > Anything new on the patchbot server status ? > > I will have physical access tomorrow.

Re: [sage-devel] patchbot server not responding

On Wed, Jul 20, 2016 at 12:39 PM, Frédéric Chapoton wrote: > Anything new on the patchbot server status ? I will have physical access tomorrow. > > Frederic > > Le jeudi 14 juillet 2016 17:53:23 UTC+2, William a écrit : >> >> On Thu, Jul 14, 2016 at 4:16 AM, Frédéric Chapoton >> wrote: >> > Sin

Re: [sage-devel] patchbot server not responding

Anything new on the patchbot server status ? Frederic Le jeudi 14 juillet 2016 17:53:23 UTC+2, William a écrit : > > On Thu, Jul 14, 2016 at 4:16 AM, Frédéric Chapoton > wrote: > > Since a few hours maybe, the patchbot server is not longer responding, > and I > > cannot connect. > > > > htt

Re: [sage-devel] patchbot server not responding

On Thu, Jul 14, 2016 at 4:16 AM, Frédéric Chapoton wrote: > Since a few hours maybe, the patchbot server is not longer responding, and I > cannot connect. > > https://patchbot.sagemath.org > > It is currently hosted at UW, I think. Thanks for reporting this. I can't do anything about this for th

[sage-devel] patchbot server not responding

Since a few hours maybe, the patchbot server is not longer responding, and I cannot connect. https://patchbot.sagemath.org It is currently hosted at UW, I think. Frederic -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

[sage-devel] patchbot arando

Hi, The patchbot arando is failing with the message File "/usr/lib/python2.7/xmlrpclib.py", line 792, in close raise ResponseError() ResponseError: ResponseError() See for instance https://patchbot.sagemath.org/log/18843/Ubuntu/14.04/i686/3.13.0-86-generic/arando/2016-06-29%2000:09:58 Coul

[sage-devel] @ patchbot breeders

Hello, to everybody running a patchbot client : *please stop your patchbots* ! Currently, every patchbot with version < 2.6.0 is not able to post to the https version of trac. Unfortunately, the patchbot version 2.6.0 is not yet easily available as an spkg. If you feel aventurous, you can try

[sage-devel] patchbot hera-optiplex

Dear all, Who is running the patchbot named Hera-Optiplex ? This patchbot is not registered in the page http://wiki.sagemath.org/buildbot/owners This patchbot currently misbehaves. Its owner is kindly asked to stop it or restart it and check that it works. Frederic -- You received this mes

[sage-devel] patchbot: Kevin should stop Athena

Hello, The Athena patchbot is completely broken. Please stop it! To avoid this I propose that after a failed build the patchbot checked that the develop branch builds cleanly. Vincent -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubsc

[sage-devel] Patchbot warnings about "increased startup time"

Hello everybody, Once in a while one of my tickets is flagged by the patchbot as "increasing startup time". Sometimes I add a function or two and thus wonder if I did something wrong, but in this specific case I am relatively confident that I didn't do anything that might have increased startup ti

Re: [sage-devel] patchbot ticket order

> > > > By the patchbot server. There are indeed some problem with the trusted > > authors and I think that most of it get solved in the last version of > > the patchbot due to Frederic Chapoton. > > Ok, so the list will be updated at one point... > As you may have remarked, the trusted list

Re: [sage-devel] patchbot ticket order

Hello Vincent, On 2015-09-15 21:14, Vincent Delecroix wrote: So the list is sorted by the first entry of the rating, the tuple and not by the score. This is only taken if the same tuple appears. Why? (And what does this tuple tell me?) The ranking is determined by the tuple and not only the sc

Re: [sage-devel] patchbot ticket order

Hello Daniel, So the list is sorted by the first entry of the rating, the tuple and not by the score. This is only taken if the same tuple appears. Why? (And what does this tuple tell me?) The ranking is determined by the tuple and not only the score (e.g. you do not want to run twice the tes

[sage-devel] patchbot ticket order

Can someone help me understand the ticket order of the patchbot. with patchbot --list (and some user defined boni) I get [2015-09-15 18:49:38 +] Launching patchbot 2.3.9 with SAGE_ROOT=/local/dakrenn/sage/patchbot [2015-09-15 18:49:38 +] Getting trusted author list... [2015-09-15 18:49

Re: [sage-devel] Patchbot reporting failed builds: Zorn

> We should try to make the patchbot safer to such building failures... > Andrew, could you give us more details about what was going wrong? I'd say that it is the usual problem: sometimes some files linger in the log/ file, and the build is reported as "failed" if some files remain there. Nathan

Re: [sage-devel] Patchbot reporting failed builds: Zorn

Honestly, I'm not entirely sure what the problem was. I killed the patchbot, did a 'make clean && make doc-clean && git checkout develop && make', and then fired it back up, and things seem to be working now. On Thu, Aug 13, 2015 at 10:12 AM, Vincent Delecroix < 20100.delecr...@gmail.com> wrote:

Re: [sage-devel] Patchbot reporting failed builds: Zorn

We should try to make the patchbot safer to such building failures... Andrew, could you give us more details about what was going wrong? On 13/08/15 16:09, Nathann Cohen wrote: Thanks ! Nathann On 13 August 2015 at 16:07, Andrew Gainer-Dewar wrote: Whoops! I think everything is fixed now. S

Re: [sage-devel] Patchbot reporting failed builds: Zorn

Thanks ! Nathann On 13 August 2015 at 16:07, Andrew Gainer-Dewar wrote: > Whoops! I think everything is fixed now. Sorry about the mess. > > --Andrew > > > On Thursday, August 13, 2015 at 5:16:03 AM UTC-4, vdelecroix wrote: >> >> Seems to be agd, see >> >> http://wiki.sagemath.org/buildbot/owner

Re: [sage-devel] Patchbot reporting failed builds: Zorn

Whoops! I think everything is fixed now. Sorry about the mess. --Andrew On Thursday, August 13, 2015 at 5:16:03 AM UTC-4, vdelecroix wrote: > > Seems to be agd, see > > http://wiki.sagemath.org/buildbot/owners > > And trac says Andrew Gainer-Dewar. > > On 13/08/15 09:34, Nathann Cohen wrote:

Re: [sage-devel] Patchbot reporting failed builds: Zorn

Seems to be agd, see http://wiki.sagemath.org/buildbot/owners And trac says Andrew Gainer-Dewar. On 13/08/15 09:34, Nathann Cohen wrote: Hello everybody, Is the owner of 'Zorn' reading this mailing list? The machine reports a build failure on a ticket, and I do not think that the errors are r

[sage-devel] Patchbot reporting failed builds: Zorn

Hello everybody, Is the owner of 'Zorn' reading this mailing list? The machine reports a build failure on a ticket, and I do not think that the errors are related: http://trac.sagemath.org/ticket/19018 Here is the bottom of the shortlog - * package: Cython log file: /mnt/pile/data

[sage-devel] Patchbot server down

http://patchbot.sagemath.org/ gives me 503 Service Unavailable -- 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

Re: [sage-devel] Patchbot librae broken

Now, the patchbot is interrupted. On 02/07/15 13:22, Jeroen Demeyer wrote: This is now blocker ticket http://trac.sagemath.org/ticket/18842 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving email

Re: [sage-devel] Patchbot librae broken

This is now blocker ticket http://trac.sagemath.org/ticket/18842 -- 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

[sage-devel] Patchbot librae broken

Several tickets that librae has tested recently fail building with Error compiling Cython file: ... include 'sage/ext/interrupt.pxi' from libc.stdint cimport uint8_t cdef class FastDigraph: cdef uint8_t n ^ ---

[sage-devel] patchbot help

I thought I would start running a patchbot, so I followed the instructions at http://wiki.sagemath.org/buildbot/details - Installed and built a new copy of Sage, latest develop branch - ./sage -i http://chapoton.perso.math.cnrs.fr/patchbot-2.3.6.spkg - make - ./sage -patchbot but I get the error

[sage-devel] patchbot vs sagedev.py doctest

Hi, i am trying to run some patchbots within a VM, i am using a ptestlong-ed version of Sage 6.7, but when the patchbot runs tests, i got an error during the test of sagedev.py (while i have no error with make ptestlong): sage -t --long --warn-long 75.9 src/sage/dev/sagedev.py ***

[sage-devel] patchbot sage4 trouble with singular (in sage/interfaces/expect.py)

Hello, The sage4 patchbot (under gentoo) has troubles with singular (see [1]) ** File "src/sage/interfaces/expect.py", line 792, in sage.interfaces.expect.Expect._eval_line Failed example: singular.interrupt(timeout=3) # som

[sage-devel] patchbot: http errors 502 or 503

Hello, While using patchbot client I do have *a lot* of http errors 502 (proxy error) or 503 (service unavailable). It happens on startup (while getting the list of trusted authors) or when transmitting report. Could somebody with access to the patchbot server could check the configurations as we

[sage-devel] Patchbot fails after first attempt

Hi there, I just installed a patchbot (2.3.1) in a clean Sage installation. After building Sage correctly (I had built it before), it failed while building the documentation with the following message: .. [reference] structure: 10 todos, 38 index, 2 citations, 37 modules [reference] tenso

Re: [sage-devel] patchbot sage4

On 2015-04-08 17:05, Jeroen Demeyer wrote: On 2015-04-07 20:39, Frédéric Chapoton wrote: sage -i http://chapoton.perso.math.cnrs.fr/patchbot-2.3.2.spkg I just installed this on arando and it doesn't work Let me add that this is a regression from patchbot-2.3.1 to patchbot-2.3.2 -- You receiv

Re: [sage-devel] patchbot sage4

On 2015-04-07 20:39, Frédéric Chapoton wrote: sage -i http://chapoton.perso.math.cnrs.fr/patchbot-2.3.2.spkg I just installed this on arando and it doesn't work, the patchbot exits immediately with Getting trusted author list... WARNING: Do not use this copy of sage while the patchbot is runni

  1   2   >