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

Restarting my "pascaline patchbot" depends on - https://trac.sagemath.org/ticket/33101 - https://trac.sagemath.org/ticket/33248 As a workaround, I can imagine creating fake lrslib and mathematica executables, placed in my PATH, that can quickly fail Sage's feature detection for lrslib and

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

2022-01-24 12:54:04 UTC, Frédéric Chapoton: > you can use the base argument in the https adress > > https://patchbot.sagemath.org/ticket/0/?base=9.5.rc1 > > But sometimes I clean old reports, keeping only very recent ones > Thanks for the tip. Cleaning up once in a while makes sense and I was

[sage-devel] Re: Patchbot/CI improvements

On Sunday, January 23, 2022 at 9:35:54 AM UTC-8 Matthias Koeppe wrote: > I don't know if Volker's integration scripts look at the patchbot status > at all > Turns out they don't. https://github.com/sagemath/git-trac-command/pull/58 fixes this -- You received this message because you are

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

you can use the base argument in the https adress https://patchbot.sagemath.org/ticket/0/?base=9.5.rc1 But sometimes I clean old reports, keeping only very recent ones Le samedi 22 janvier 2022 à 14:54:40 UTC+1, Samuel Lelievre a écrit : > Hi Frédéric, > > Thanks for the link! Hope the branch

[sage-devel] Re: Patchbot/CI improvements

On Monday, January 24, 2022 at 2:35:54 AM UTC+9 Matthias Koeppe wrote: > 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 think

[sage-devel] Re: Patchbot/CI improvements

And here is one so that on merge conflicts, there is no manual work for the release managers, and developers get some information about the conflict other than "merge conflict". https://github.com/sagemath/git-trac-command/pull/57 On Sunday, January 23, 2022 at 1:18:40 PM UTC-8 Matthias Koeppe

[sage-devel] Re: Patchbot/CI improvements

I have also prepared a PR for the "git releasemgr" scripts to make it easier to merge only tickets in the current milestone. https://github.com/sagemath/git-trac-command/pull/54 On Sunday, January 23, 2022 at 9:35:54 AM UTC-8 Matthias Koeppe wrote: > Patchbot experts: > 1) Currently the

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

On Fri, 21 Jan 2022, 11:16 Dima Pasechnik, wrote: > On Fri, Jan 21, 2022 at 9:43 AM 'jonatha...@googlemail.com' via > sage-devel wrote: > > > > Hi Frédéric, > > > > due to https://trac.sagemath.org/ticket/33027 I have given up on > running my patchbot. > > I've made this ticket a blocker. > >

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

Hi Frédéric, Thanks for the link! Hope the branch at that ticket gets merged in the next development release. Tried building Sage 9.5.rc3 but hit the sagemath_doc_html build failure reported at ticket #33139. Are the reports at https://patchbot.sagemath.org/ticket/0/ only visible until the next

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

lrslib doctests in game_theory/parser.py are fixed in #33101 (positive review) Le vendredi 21 janvier 2022 à 13:40:17 UTC+1, Samuel Lelievre a écrit : > Hi Frédéric, > > I have upgraded to sage-patchbot 3.0.4 on "pascaline". > > On Sage 9.5.rc2, "ticket 0" failed with >

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

Hi Frédéric, I have upgraded to sage-patchbot 3.0.4 on "pascaline". On Sage 9.5.rc2, "ticket 0" failed with -- SEED=94195001484901963602666886307845237936 alias sagetest=".sage -t --long --random-seed=$SEED" sagetest

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

On Fri, Jan 21, 2022 at 9:43 AM 'jonatha...@googlemail.com' via sage-devel wrote: > > Hi Frédéric, > > due to https://trac.sagemath.org/ticket/33027 I have given up on running my > patchbot. I've made this ticket a blocker. Everyone who has an idea about sage-cleaner, please have a look.

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

Hi Frédéric, due to https://trac.sagemath.org/ticket/33027 I have given up on running my patchbot. Jonathan Frédéric Chapoton schrieb am Montag, 17. Januar 2022 um 21:31:31 UTC+1: > and to fix the remaining doc-cleaning issue, please upgrade again to the > master branch of github (aka tag

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

and to fix the remaining doc-cleaning issue, please upgrade again to the master branch of github (aka tag 3.0.4) (I would appreciate answers, rather than full silence) Frédéric Le vendredi 14 janvier 2022 à 21:25:11 UTC+1, Frédéric Chapoton a écrit : > also patchbots have persistent problems

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

also patchbots have persistent problems with building docs. Can the people that changed something to doc-building please repair the patchbot accordingly ? pull request on github, please https://patchbot.sagemath.org/ticket/33157/ Le vendredi 14 janvier 2022 à 17:40:27 UTC+1, Frédéric Chapoton

[sage-devel] Re: patchbot trouble

removing the file `not_tested.py` seems to help. Martin R schrieb am Donnerstag, 2. September 2021 um 10:10:13 UTC+2: > 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

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

Yes, I will give that a try. Thanks. By searching through the patchbot logs in reverse, I also found the ticket that was causing the infinite print loop: https://trac.sagemath.org/ticket/19025 . -- You received this message because you are subscribed to

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

If your patchbot runs only at certain hours of the day, you could also clear /tmp daily before patchbot starts, using a cronjob. -- 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,

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

Possibly related: - https://github.com/sagemath/sage-patchbot/issues/130 Feel free to open another issue or to send a pull request if you see how to fix any known patchbot issue. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

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

Thank you for the note. I have disabled this patchbot client for now. The problem seems to be that the /tmp directory gets flooded with thousands of little files that do not get removed automatically. It has been less than two weeks since I have last cleared the /tmp directory, and now there

[sage-devel] Re: patchbot security

Thanks, I have to see what I can do about it (I went through all the tickets I tested and it looks things are fine). Am Samstag, 6. Juli 2019 14:50:51 UTC+2 schrieb Volker Braun: > > The patchbot configuration has some options for trusting specific user > accounts. > > Having said that, you are

[sage-devel] Re: patchbot security

The patchbot configuration has some options for trusting specific user accounts. Having said that, you are correct in that it executes code submitted by strangers over the internet. At the very least make a separate user account for running the patchbot. You might want to add an additional

[sage-devel] Re: patchbot server down

In my case it crashed (might have been because I tried to start it during downtime). By looking at https://patchbot.sagemath.org/machines I'm having the impression that I'm not the only one, where this happened. Am Samstag, 6. Juli 2019 07:46:41 UTC+2 schrieb Frédéric Chapoton: > > No. No need

[sage-devel] Re: patchbot server down

No. No need to restart any patchbot client. F Le samedi 6 juillet 2019 07:17:59 UTC+2, Jonathan Kliem a écrit : > > Great, > > so I guess all patchbots have to be restarted (if not already done so). > -- You received this message because you are subscribed to the Google Groups "sage-devel"

[sage-devel] Re: patchbot server down

Great, so I guess all patchbots have to be restarted (if not already done so). -- 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] Re: patchbot server down

yes, yes... This was my tentative of upgrading ubuntu on the server, with unexpected consequences. The server is now working again, after a struggle together with Thierry. F Le vendredi 5 juillet 2019 15:49:52 UTC+2, Jonathan Kliem a écrit : > > https://patchbot.sagemath.org/ displays an > >

[sage-devel] Re: Patchbot zancara: Disk quota exceeded

I just saw this. Wasn't subscribed back then. But I noticed that my home was full :-) This is solved now. I had to change DOT_SAGE and CCACHE_DIR, as I only have very limited amount of memory in home. Maybe this is worth mentioning in the wiki https://wiki.sagemath.org/patchbot Even though I

[sage-devel] Re: patchbot problems

On Tue, Jan 23, 2018 at 10:46 AM, Erik Bray wrote: > On Mon, Jan 22, 2018 at 11:52 AM, Erik Bray wrote: >> Hi all, >> >> I noticed this morning that the patchbot was returning error 500s upon >> listing open tickets. I realized after some

[sage-devel] Re: patchbot problems

On Mon, Jan 22, 2018 at 11:52 AM, Erik Bray wrote: > 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

Re: [sage-devel] Re: patchbot problems

On Mon, Jan 22, 2018 at 1:08 PM, Dima Pasechnik wrote: > IMHO already for quite some time 1GB of RAM might not be enough to build > Sage docs, in particular if you run with -jX and X>1... I'm talking about the patchbot.sagemath.org server--it doesn't build anything. > On

[sage-devel] Re: patchbot problems

IMHO already for quite some time 1GB of RAM might not be enough to build Sage docs, in particular if you run with -jX and X>1... On Monday, January 22, 2018 at 10:52:57 AM UTC, Erik Bray wrote: > > Hi all, > > I noticed this morning that the patchbot was returning error 500s upon > listing

Re: [sage-devel] Re: patchbot server down

I'm sorry you spent any time on it... Like I said, I was working on it :) Fixed now. On Fri, Oct 13, 2017 at 11:04 AM, Frédéric Chapoton wrote: > I have failed to find the issue.. > > > Le vendredi 13 octobre 2017 10:29:03 UTC+2, Erik Bray a écrit : >> >>

[sage-devel] Re: patchbot server down

I have failed to find the issue.. Le vendredi 13 octobre 2017 10:29:03 UTC+2, Erik Bray a écrit : > > 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

[sage-devel] Re: Patchbot failures metaticket

Mon 2017-09-11 16:59:48 UTC, Maarten Derickx: > p.s. Tips on how to search for tickets on trac are welcome! Trac has both a search feature and a (much more powerful) query feature: - https://trac.sagemath.org/search - https://trac.sagemath.org/query See some examples of using the query feature

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

2) It is unsafe because it modifies src/bin. 1) This is the expected behaviour. The pending report will disappear after some time. Le vendredi 11 août 2017 19:34:51 UTC+2, Maarten Derickx a écrit : > > Hi, > > At https://patchbot.sagemath.org/ticket/23610/ you can see that the > patchbot

Re: [sage-devel] Re: Patchbot monitoring

On Fri, Jun 30, 2017 at 4:04 PM, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > On 30/06/2017 13:53, Erik Bray wrote: >> >> On Fri, Jun 30, 2017 at 12:35 PM, Kwankyu Lee wrote: >>> >>> >>> >>> On Friday, June 30, 2017 at 9:54:00 AM UTC+2, Erik Bray wrote:

Re: [sage-devel] Re: Patchbot monitoring

On 30/06/2017 13:53, Erik Bray wrote: On Fri, Jun 30, 2017 at 12:35 PM, Kwankyu Lee wrote: On Friday, June 30, 2017 at 9:54:00 AM UTC+2, Erik Bray wrote: Does anyone who runs / administers Sage patchbots have any hints/tips regarding monitoring of their patchbots? I

Re: [sage-devel] Re: Patchbot monitoring

On Fri, Jun 30, 2017 at 12:35 PM, Kwankyu Lee wrote: > > > On Friday, June 30, 2017 at 9:54:00 AM UTC+2, Erik Bray wrote: >> >> Does anyone who runs / administers Sage patchbots have any hints/tips >> regarding monitoring of their patchbots? > > > I run a patchbot using

[sage-devel] Re: Patchbot monitoring

On Friday, June 30, 2017 at 9:54:00 AM UTC+2, Erik Bray wrote: > > Does anyone who runs / administers Sage patchbots have any hints/tips > regarding monitoring of their patchbots? > I run a patchbot using screen. 1. I use "screen -r" to see what the patchbot is doing currently. 2. I check

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

On 2017-01-08 07:21, Clemens Heuberger wrote: >>> However, if I understand the code correctly, the patchbot should at least >>> see >>> the ticket and report >>> "do not test if some author is not trusted" >>> , which it does not in my case. It's simply not in the downloaded file, its >>>

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

On 2017-01-07 23:22, Vincent Delecroix wrote: > Le 05/01/2017 à 18:05, Clemens Heuberger a écrit : >> >> Hello, >> >> On 2017-01-05 17:29, Frédéric Chapoton wrote: >>> Tickets with untrusted authors are never looked at, unless you ask >>> specifically so : >>> { >>> "Clemens Heuberger":

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

Le 05/01/2017 à 18:05, Clemens Heuberger a écrit : Hello, On 2017-01-05 17:29, Frédéric Chapoton wrote: Tickets with untrusted authors are never looked at, unless you ask specifically so : { "Clemens Heuberger": "trusted", "Roswitha Rissner": "not trusted" } that's clear. My

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

Hello, On 2017-01-05 17:29, Frédéric Chapoton wrote: > Tickets with untrusted authors are never looked at, unless you ask > specifically so : > { > "Clemens Heuberger": "trusted", > "Roswitha Rissner": "not trusted" > } that's clear. My config.json has

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

Hello, Tickets with untrusted authors are never looked at, unless you ask specifically so : { "Clemens Heuberger": "trusted", "Roswitha Rissner": "not trusted" } Frederic Le jeudi 5 janvier 2017 16:00:53 UTC+1, Clemens Heuberger a écrit : > > I am playing around with a patchbot and I

Re: [sage-devel] Re: patchbot server not responding

Hi, On Tue, Jul 26, 2016 at 11:46:03AM -0700, Frédéric Chapoton wrote: > Hello, > > I can log on patchbot.sagemath.org (as well as R. Bradshaw, R. A. Ohana and > M. Marco) > > I do not have the technical comptetence to move the patchbot server > elsewhere. This probably involves at least

Re: [sage-devel] Re: patchbot server not responding

Hello, I can log on patchbot.sagemath.org (as well as R. Bradshaw, R. A. Ohana and M. Marco) I do not have the technical comptetence to move the patchbot server elsewhere. This probably involves at least setting up a web server and copying the report database (which is at least 20GB large,

Re: [sagemath-admins] Re: [sage-devel] Re: patchbot server not responding

On Fri, Jul 22, 2016 at 9:44 AM, Samuel Lelièvre wrote: >> I can log in. Andrew Ohana was the one to give me access. >> He told me the other people with access were himself, Harald and Volker. >> I asked about adding more people, he said fine as long as Harald agrees,

Re: [sagemath-admins] Re: [sage-devel] Re: patchbot server not responding

2016-07-22 9:19 GMT+02:00 Samuel Lelièvre: > I can log in. Andrew Ohana was the one to give me access. > He told me the other people with access were himself, Harald and Volker. > I asked about adding more people, he said fine as long as Harald agrees, > so Harald is the boss there. My answer

Re: [sagemath-admins] Re: [sage-devel] Re: patchbot server not responding

I can log in. Andrew Ohana was the one to give me access. He told me the other people with access were himself, Harald and Volker. I asked about adding more people, he said fine as long as Harald agrees, so Harald is the boss there. Samuel 2016-07-21 20:55 GMT+02:00 William Stein

Re: [sage-devel] Re: patchbot server not responding

I can log in on fileserver.sagemath.org; This is the machine where I upload sage and third-party tarballs, it then feeds it to the mirrors. I don't know the details about the mirroring, I think Harald set that up. On Thursday, July 21, 2016 at 8:56:19 PM UTC+2, William wrote: > > Hi, > > I

Re: [sage-devel] Re: patchbot server not responding

Hi, I rebooted the host machine and both fileserver.sagemath.org and patchbot.sagemath.org respond to ssh requests. I do NOT have any clue how to actually login to either machine. I was also completely unable to login to the machine that hosts them as well. Yes, I tried using a rescue disk and

[sage-devel] Re: patchbot server not responding

Volker Braun wrote: > Please check up on fileserver.sagemath.org, too, while you are at it... Yes, their IPs differ by just one... ;-) -leif > 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 >

Re: [sage-devel] Re: patchbot arando

Le mercredi 29 juin 2016 11:33:53 UTC+2, Jeroen Demeyer a écrit : > > > I'm on holidays now, I just stopped the bot. > > Thanks! Sorry for having disturbed you during holidays... Best wishes, Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel"

Re: [sage-devel] Re: patchbot arando

On 2016-06-29 11:27, Frédéric Chapoton wrote: Yes. Jeroen is aware of the problem, but not acting to solve it by stopping or updating his patchbot. I may have to ban arando. I'm on holidays now, I just stopped the bot. -- You received this message because you are subscribed to the Google

Re: [sage-devel] Re: patchbot arando

On Wed, Jun 29, 2016 at 11:27 AM, Frédéric Chapoton wrote: > Yes. Jeroen is aware of the problem, but not acting to solve it by stopping > or updating his patchbot. I may have to ban arando. See also:

[sage-devel] Re: patchbot arando

Yes. Jeroen is aware of the problem, but not acting to solve it by stopping or updating his patchbot. I may have to ban arando. Frederic. Le mercredi 29 juin 2016 11:21:27 UTC+2, Eric Gourgoulhon a écrit : > > Hi, > > The patchbot arando is failing with the message > > File

[sage-devel] Re: patchbot hera-optiplex

Hello. The patchbot named 'hera-OptiPlex-7010' is now blacklisted (tentatively). In principle, it can no longer posts its reports. Let us see what happens. If you own this bot, please contact me. I am not happy with that banning, because there are only 4 patchbots running, so now only 3

[sage-devel] Re: patchbot hera-optiplex

Hi, I confirm that the patchbot hera-OptiPlex-7010 misbehaves: it systematically returns "build failed" with the message The content of "/home/hera/sage-patchbot/build/pkgs/r_jupyter/type" must be 'base', 'standard', 'optional', 'experimental' or 'pip' Apply -- 4 seconds Traceback (most recent

[sage-devel] Re: patchbot hera-optiplex

On Wednesday, 30 December 2015 18:06:22 UTC, Frédéric Chapoton wrote: > > 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

[sage-devel] Re: patchbot says ValueError: {} inserted on {} non-empty lines

Thanks for the report. Correction done. Will appear in a later version of the patchbot. Frederic Le mardi 22 décembre 2015 22:33:05 UTC+1, Sébastien Labbé a écrit : > > Oups, I wanted to post this on sage-devel. Sorry. > > Sébastien > > On Tuesday, December 22, 2015 at 10:30:10 PM UTC+1,

[sage-devel] Re: patchbot says ValueError: {} inserted on {} non-empty lines

Oups, I wanted to post this on sage-devel. Sorry. Sébastien On Tuesday, December 22, 2015 at 10:30:10 PM UTC+1, Sébastien Labbé wrote: > > Hello patchbot developers, > > At http://patchbot.sagemath.org/ticket/13580/, before the doctest > continuation problem was fixed, the patchbot was

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

Because this is a very flaky plugin, its results must be human-interpreted and not taken a a rule of law. More generally, the patchbots are there to warn you, but full green light is not a mandatory requirement. Le mardi 10 novembre 2015 21:58:45 UTC+1, Nathann Cohen a écrit : > > Hello

[sage-devel] Re: patchbot vs sagedev.py doctest

Hello, I would like to second this demand. I have not been able to understand what is going wrong here. if somebody understanding the dev scripts could say a word, that would be nice.. This issue is preventing two patchbot instances to run, and we are currently lacking them much. Frederic Le

[sage-devel] Re: patchbot vs sagedev.py doctest

Its possible that this is just a symptom of a corruption that happened elsewhere. The patchbot should perhaps run some clean-up on the git repo before each build attempt to start from a known state. E.g. git fsck --full git stash clear On Monday, August 3, 2015 at 8:34:25 PM

[sage-devel] Re: Patchbot librae broken

ARggg... I was precisely posting about that simultaneously ^^; https://groups.google.com/forum/#!topic/sage-devel/LFdGLWpU5s4 It is not because of any specific ticket. It is because of #18746, which they tested in the past, and the cython files they cached when they did. Nathann -- You

Re: [sage-devel] Re: patchbot help

Sorry not to have responded today, I have been otherwise occupied. There is nothing customised at all. I don't have time to track this down in the near future so I will just give up for now. John On 17 June 2015 at 13:22, Frédéric Chapoton fchapot...@gmail.com wrote: Do you have a custom

Re: [sage-devel] Re: patchbot help

Do you have a custom matplotlibrc ? Le mercredi 17 juin 2015 12:35:59 UTC+2, Frédéric Chapoton a écrit : Maybe ticket #12114 is relevant.. Le mercredi 17 juin 2015 12:22:13 UTC+2, Frédéric Chapoton a écrit : The plot failures are correlated exactly to the files where pylab is imported..

Re: [sage-devel] Re: patchbot help

Maybe this page is relevant about the matplotlib failures ? http://stackoverflow.com/questions/2443702/problem-running-python-matplotlib-in-background-after-ending-ssh-session Le mercredi 17 juin 2015 12:04:58 UTC+2, Frédéric Chapoton a écrit : Hello, Indeed, the patchbot stops if he fails

Re: [sage-devel] Re: patchbot help

The plot failures are correlated exactly to the files where pylab is imported.. Le mercredi 17 juin 2015 12:07:17 UTC+2, Frédéric Chapoton a écrit : Maybe this page is relevant about the matplotlib failures ?

Re: [sage-devel] Re: patchbot help

Hello, Indeed, the patchbot stops if he fails to run the 0 ticket (i.e. latest develop) without failures. Otherwise it would send many bad reports.. Have you many installed optional packages ? Could you please - run yourself sage -t --long --warn-long 58.6 src/sage/plot/plot.py - post here the

Re: [sage-devel] Re: patchbot help

Maybe ticket #12114 is relevant.. Le mercredi 17 juin 2015 12:22:13 UTC+2, Frédéric Chapoton a écrit : The plot failures are correlated exactly to the files where pylab is imported.. Le mercredi 17 juin 2015 12:07:17 UTC+2, Frédéric Chapoton a écrit : Maybe this page is relevant about the

Re: [sage-devel] Re: patchbot help

On 16 June 2015 at 16:12, Thierry sage-googlesu...@lma.metelu.net wrote: Hi, if your machine is named lehner (which is likely since both have user indeed it is: lehner.warwick.ac.uk at IP 137.205.56.253 jec), then you have some failing doctests while running the patchbot:

Re: [sage-devel] Re: patchbot help

John, Occam's Razor would suggest that those timeouts are because the machine is too much loaded. If you are using many parallel threads (MAKE=make -jN for a high value of N) or somebody is running other things on that machine, that might explain the timeouts. Can you send the log file on

Re: [sage-devel] Re: patchbot help

Hi, if your machine is named lehner (which is likely since both have user jec), then you have some failing doctests while running the patchbot: http://patchbot.sagemath.org/log/0/Ubuntu/14.04/x86_64/3.13.0-48-generic/lehner/2015-06-15%2023:18:15%20+0100 I have the same issue of having no failing

Re: [sage-devel] Re: patchbot help

On 16 June 2015 at 17:27, Jeroen Demeyer jdeme...@cage.ugent.be wrote: John, Occam's Razor would suggest that those timeouts are because the machine is too much loaded. If you are using many parallel threads (MAKE=make -jN for a high value of N) or somebody is running other things on that

Re: [sage-devel] Re: patchbot help

On 2015-06-16 20:26, John Cremona wrote: http://homepages.warwick.ac.uk/staff/J.E.Cremona/ptestlong.log.bz2 There is nothing suspicious in that file, I don't know what the cause is... -- You received this message because you are subscribed to the Google Groups sage-devel group. To

Re: [sage-devel] Re: patchbot help

On 14 June 2015 at 22:22, John Cremona john.crem...@gmail.com wrote: On 14 June 2015 at 20:33, Frédéric Chapoton fchapot...@gmail.com wrote: This should work.. Is there anything in the required directory ? Are you sure you are calling the right sage ? not another one without the patchbot

[sage-devel] Re: patchbot help

This should work.. Is there anything in the required directory ? Are you sure you are calling the right sage ? not another one without the patchbot installed ? Le dimanche 14 juin 2015 21:03:33 UTC+2, John Cremona a écrit : I thought I would start running a patchbot, so I followed the

Re: [sage-devel] Re: patchbot help

On 14 June 2015 at 20:33, Frédéric Chapoton fchapot...@gmail.com wrote: This should work.. Is there anything in the required directory ? Are you sure you are calling the right sage ? not another one without the patchbot installed ? Sorry, In did install into the wrong copy. It is starting to

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

Actually librae as well... sage -t --long src/sage/interfaces/expect.py ** File src/sage/interfaces/expect.py, line 792, in sage.interfaces.expect.Expect._eval_line Failed example: singular.interrupt(timeout=3) # sometimes

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

seems to be #10476 On 16/05/15 21:27, Vincent Delecroix wrote: Actually librae as well... sage -t --long src/sage/interfaces/expect.py ** File src/sage/interfaces/expect.py, line 792, in

[sage-devel] Re: Patchbot fails after first attempt

Okay, for the time being I am just excluding this ticket manually by adding in extra line in get_ticket. Am Dienstag, 21. April 2015 16:33:16 UTC+2 schrieb Frédéric Chapoton: Or maybe it can, with something like {bonus:{Bouillaguet:-1000}} inside config.json Frederic Le mardi 21 avril

[sage-devel] Re: Patchbot fails after first attempt

Another issue has come up. My patchbot seems to be fascinated by 15209 and keeps retesting it, see http://patchbot.sagemath.org/ticket/15209/ Any suggestions? Am Dienstag, 14. April 2015 16:15:00 UTC+2 schrieb Frédéric Chapoton: Great ! I am happy every time I see a green blob ! In

[sage-devel] Re: Patchbot fails after first attempt

Yes, I have seen that this morning. It loops because the Spkg do not make true reports, so it thinks it has not done anything on that ticket. It only happens because it does not find any better ticket to work on, I think. I have modified the patchbot code to avoid that, changes will be in the

[sage-devel] Re: Patchbot fails after first attempt

Or maybe it can, with something like {bonus:{Bouillaguet:-1000}} inside config.json Frederic Le mardi 21 avril 2015 16:24:08 UTC+2, Frédéric Chapoton a écrit : Hmm, sorry, it seems that there is no clear way to skip a chosen ticket.. So the json config file will not help. Le mardi 21

[sage-devel] Re: Patchbot fails after first attempt

Hmm, sorry, it seems that there is no clear way to skip a chosen ticket.. So the json config file will not help. Le mardi 21 avril 2015 16:15:41 UTC+2, Frédéric Chapoton a écrit : Yes, I have seen that this morning. It loops because the Spkg do not make true reports, so it thinks it has not

Re: [sage-devel] Re: Patchbot fails after first attempt

--skip-base only disables the initial run (which is useful for preventing a rogue/broken install from declaring all tickets as broken). On Tue, Apr 14, 2015 at 2:49 AM, Jan Keitel jocalareanetw...@gmail.com wrote: Whatever the problem was before, it is gone now - at least it just successfully

[sage-devel] Re: Patchbot fails after first attempt

Whatever the problem was before, it is gone now - at least it just successfully tested #18159. When running the patchbot with skip-base, should I make sure that I update the patchbot/base branch regularly or is that done automatically? Many thanks, Jan Am Montag, 13. April 2015 21:39:06 UTC+2

[sage-devel] Re: Patchbot fails after first attempt

Great ! I am happy every time I see a green blob ! In principle, it should update itself at every develop release. But let us see what happen when 6.7.beta0 is out. Frederic Le mardi 14 avril 2015 11:49:48 UTC+2, Jan Keitel a écrit : Whatever the problem was before, it is gone now - at least

[sage-devel] Re: Patchbot fails after first attempt

Could you maybe take a look at the patchbot logs? At the moment, there are: http://patchbot.sagemath.org/ticket/15047/ http://patchbot.sagemath.org/ticket/18176/ http://patchbot.sagemath.org/ticket/9903/ In every case my local log is 3GiB big and if it continues at that rate, my hd will soon

[sage-devel] Re: Patchbot fails after first attempt

I do not understand either. And the log is too big, it freezes my browser when I try to have a look. Let us try something else: Could you please 1) update to patchbot 2.3.2 sage -i http://chapoton.perso.math.cnrs.fr/patchbot-2.3.2.spkg 2) pull the develop branch of sage git pull trac develop

[sage-devel] Re: Patchbot fails after first attempt

Thanks for the quick replies and yes, I did indeed run sage -patchbot. The problem seemed to disappear after running ./sage -patchbot a second time, so I'm not sure that I can reproduce it without a new installation. Volker's suggestion sounds reasonable, though. But since I'm at it, another

[sage-devel] Re: Patchbot fails after first attempt

Hello, concerning Volker suggestion, the patchbot already does a make doc-clean. I do not understand what failed with your first run. concerning the large log, indeed this seems huge. But not so-harmless ticket 15047 is depending on 18155, which implies a lot of rebuilding. And you are based

[sage-devel] Re: Patchbot fails after first attempt

Hello, thanks for the feedback. I guess you just ran sage -patchbot ? could you please try to run sage -patchbot --safe-only or sage -patchbot --skip-base and tell me what happens ? Another sanity check would be sage -patchbot --skip-base --plugin-only --ticket=18177 or whatever ticket

[sage-devel] Re: Patchbot fails after first attempt

No worries, thanks for all the support. I'll try a clean install again tomorrow and this time, I'll save the full log. As far as 15047 is concerned, apparently the log did get uploaded and patchbot is happily testing away on the next ticket. Am Montag, 13. April 2015 16:39:37 UTC+2 schrieb

Re: [sage-devel] Re: patchbot sage4

oops, sorry. Indeed *skip-base* and *safe-only* do not take an argument. I think I have found and corrected the problem. Should be in the next release. Do you happen to know who runs pi, grobner, sage4 and so on ? Frederic Le jeudi 9 avril 2015 09:42:56 UTC+2, Jeroen Demeyer a écrit : On

Re: [sage-devel] Re: patchbot sage4

@the owner of patchbot *sage4:* your bot is now stuck on #18131. It seems that the problem is with unsafe tickets. Could you please tell me what sage -patchbot --skip-base --safe-only --ticket=18131 does ? Le mercredi 8 avril 2015 20:56:33 UTC+2, Frédéric Chapoton a écrit : Hello, Could

Re: [sage-devel] Re: patchbot sage4

On 2015-04-08 20:56, Frédéric Chapoton wrote: ./sage -patchbot --skip-base=True patchbot.py: error: --skip-base option does not take a value With ./sage -patchbot --skip-base, the patchbot starts to run... -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] Re: patchbot sage4

On 2015-04-09 10:18, Frédéric Chapoton wrote: oops, sorry. Indeed *skip-base* and *safe-only* do not take an argument. I think I have found and corrected the problem. Should be in the next release. Do you happen to know who runs pi, grobner, sage4 and so on ? sage4 is me, the rest I don't

Re: [sage-devel] Re: patchbot sage4

On 2015-04-08 18:05, Frédéric Chapoton wrote: What command exactly did you run ? nice ./sage --patchbot Did you choose a specific ticket ? No. Could you please try to use the patchbot 2.3.2 with safe-only set to False ? I have no idea what that means. -- You received this message because

  1   2   3   >