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 next release. Right now, you can exclude this ticket in the bot config json file. This probably requires to stop the bot and relaunch it with a config file chosen using --config=CONFIG specify the config file Frederic Le mardi 21 avril 2015 16:06:30 UTC+2, Jan Keitel a écrit : > > 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 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 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 schrieb Frédéric Chapoton: >>>> >>>> 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 >>>> git ch develop -b patchbot/base >>>> 3) run the patchbot with sage -patchbot --skip-base ? >>>> >>>> Fred >>>> >>>> Le lundi 13 avril 2015 21:03:44 UTC+2, Jan Keitel a écrit : >>>>> >>>>> 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 be full. I'm not sure what's going wrong. >>>>> >>>>> Best, >>>>> Jan >>>>> >>>>> Am Montag, 13. April 2015 17:28:52 UTC+2 schrieb Jan Keitel: >>>>>> >>>>>> 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 Frédéric Chapoton: >>>>>>> >>>>>>> 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 on master, which also means a lot of >>>>>>> stuff >>>>>>> has changed since 6.5. >>>>>>> >>>>>>> In case the bot fails on the current ticket, I would suggest to use >>>>>>> sage -patchbot --safe-only >>>>>>> >>>>>>> There is a patchbot 2.3.2 available, but it will only work with sage >>>>>>> -patchbot --skip-base >>>>>>> >>>>>>> sorry for the trouble. I try do do my best to enhance the patchbot, >>>>>>> but there may be some road bumps during the process. >>>>>>> >>>>>>> Frederic >>>>>>> >>>>>>> Le lundi 13 avril 2015 16:27:23 UTC+2, Jan Keitel a écrit : >>>>>>>> >>>>>>>> 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 question: It has now been testing the >>>>>>>> first real ticket for some time (the harmless looking 15047), but >>>>>>>> already >>>>>>>> produced a 3GiB logfile. Is that sort of behavior normal? I'm >>>>>>>> wondering >>>>>>>> what is going to happen once it starts uploading this to the server: >>>>>>>> >>>>>>>> jkeitel@pcl337b:~/sage/sage_patchbot/logs/patchbot> ls -l >>>>>>>> total 3100488 >>>>>>>> drwxr-xr-x 2 jkeitel THEORY2 4096 Apr 13 14:52 0 >>>>>>>> -rw-r--r-- 1 jkeitel THEORY2 1268342 Apr 13 15:32 0-log.txt >>>>>>>> -rw-r--r-- 1 jkeitel THEORY2 3173617322 Apr 13 16:26 15047-log.txt >>>>>>>> -rw-r--r-- 1 jkeitel THEORY2 168 Apr 13 15:33 history.txt >>>>>>>> >>>>>>>> Am Montag, 13. April 2015 15:52:03 UTC+2 schrieb Frédéric Chapoton: >>>>>>>>> >>>>>>>>> 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 you want. >>>>>>>>> >>>>>>>>> Frederic >>>>>>>>> Le lundi 13 avril 2015 14:51:53 UTC+2, Jan Keitel a écrit : >>>>>>>>>> >>>>>>>>>> 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] tensor: 0 todos, 4 index, 0 citations, 3 modules >>>>>>>>>> [reference] tensor_free_modules: >>>>>>>>>> [reference] WARNING: Unable to fetch >>>>>>>>>> /home/pcl337b/jkeitel/sage/sage_patchbot/src/doc/output/doctrees/en/reference/tensor_free_modules/environment.pickle >>>>>>>>>> Error building the documentation. >>>>>>>>>> Traceback (most recent call last): >>>>>>>>>> File >>>>>>>>>> "/home/pcl337b/jkeitel/sage/sage_patchbot/src/doc/common/builder.py", >>>>>>>>>> line >>>>>>>>>> 1618, in <module> >>>>>>>>>> getattr(get_builder(name), type)() >>>>>>>>>> File >>>>>>>>>> "/home/pcl337b/jkeitel/sage/sage_patchbot/src/doc/common/builder.py", >>>>>>>>>> line >>>>>>>>>> 292, in _wrapper >>>>>>>>>> getattr(get_builder(document), 'inventory')(*args, **kwds) >>>>>>>>>> File >>>>>>>>>> "/home/pcl337b/jkeitel/sage/sage_patchbot/src/doc/common/builder.py", >>>>>>>>>> line >>>>>>>>>> 516, in _wrapper >>>>>>>>>> getattr(DocBuilder(self.name, lang), format)(*args, **kwds) >>>>>>>>>> File >>>>>>>>>> "/home/pcl337b/jkeitel/sage/sage_patchbot/src/doc/common/builder.py", >>>>>>>>>> line >>>>>>>>>> 110, in f >>>>>>>>>> eval(compile(open(sys.argv[0]).read(), sys.argv[0], 'exec')) >>>>>>>>>> File >>>>>>>>>> "/home/pcl337b/jkeitel/sage/sage_patchbot/src/doc/common/custom-sphinx-build.py", >>>>>>>>>> >>>>>>>>>> line 219, in <module> >>>>>>>>>> raise OSError(ERROR_MESSAGE) >>>>>>>>>> OSError: [reference] WARNING: Unable to fetch >>>>>>>>>> /home/pcl337b/jkeitel/sage/sage_patchbot/src/doc/output/doctrees/en/reference/tensor_free_modules/environment.pickle >>>>>>>>>> >>>>>>>>>> make: *** [doc-html] Error 1 >>>>>>>>>> Apply -- 0 seconds >>>>>>>>>> Traceback (most recent call last): >>>>>>>>>> File >>>>>>>>>> "/home/pcl337b/jkeitel/sage/sage_patchbot/local/bin/patchbot/patchbot.py", >>>>>>>>>> >>>>>>>>>> line 550, in test_a_ticket >>>>>>>>>> do_or_die("$MAKE") >>>>>>>>>> File >>>>>>>>>> "/home/pcl337b/jkeitel/sage/sage_patchbot/local/bin/patchbot/util.py", >>>>>>>>>> line >>>>>>>>>> 141, in do_or_die >>>>>>>>>> raise exn_class("%s %s" % (res, cmd)) >>>>>>>>>> Exception: 512 $MAKE >>>>>>>>>> 2015-04-13 14:41:39 +0200 >>>>>>>>>> 1347 seconds >>>>>>>>>> Traceback (most recent call last): >>>>>>>>>> File >>>>>>>>>> "/home/pcl337b/jkeitel/sage/sage_patchbot/local/bin/patchbot/patchbot.py", >>>>>>>>>> >>>>>>>>>> line 550, in test_a_ticket >>>>>>>>>> do_or_die("$MAKE") >>>>>>>>>> File >>>>>>>>>> "/home/pcl337b/jkeitel/sage/sage_patchbot/local/bin/patchbot/util.py", >>>>>>>>>> line >>>>>>>>>> 141, in do_or_die >>>>>>>>>> raise exn_class("%s %s" % (res, cmd)) >>>>>>>>>> Exception: 512 $MAKE >>>>>>>>>> Reporting 0 BuildFailed >>>>>>>>>> REPORT >>>>>>>>>> {'base': '6.5', >>>>>>>>>> 'deps': [], >>>>>>>>>> 'git_base': 'e88642d0ec3dc79278b8828a0b91e5d2d654d17a', >>>>>>>>>> 'git_base_human': '6.5', >>>>>>>>>> 'git_branch': 'master', >>>>>>>>>> 'git_commit': 'e88642d0ec3dc79278b8828a0b91e5d2d654d17a', >>>>>>>>>> 'git_log': [], >>>>>>>>>> 'git_merge': 'e88642d0ec3dc79278b8828a0b91e5d2d654d17a', >>>>>>>>>> 'machine': ['openSUSE ', '13.1', 'x86_64', '3.11.10-25-desktop', >>>>>>>>>> 'pcl337b'], >>>>>>>>>> 'patchbot_version': '2.3.1', >>>>>>>>>> 'patches': [], >>>>>>>>>> 'plugins': [], >>>>>>>>>> 'spkgs': [], >>>>>>>>>> 'status': 'BuildFailed', >>>>>>>>>> 'time': '2015-04-13 14:41:41 +0200', >>>>>>>>>> 'user': 'jkeitel'} >>>>>>>>>> 0 BuildFailed >>>>>>>>>> ok >>>>>>>>>> Done reporting 0 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Current base: git://github.com/sagemath/sage.git master >>>>>>>>>> Failing tests in your base install: exiting. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> After running ./sage -patchbot a second time, it seems to have >>>>>>>>>> been able to build the documentation, but I still wanted to report >>>>>>>>>> this. I >>>>>>>>>> might not have built the documentation when building Sage before, >>>>>>>>>> but >>>>>>>>>> shouldn't the patchbot notice this by itself? >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Jan >>>>>>>>>> >>>>>>>>> -- 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/d/optout.
