On Wed, Feb 15, 2012 at 10:31 AM, kcrisman <kcris...@gmail.com> wrote: >> > expected behavior. >> >> It does always timeout. The regular doctests take 1300 seconds for >> sandpile.py! I need to figure out what's going on there. >> >> > I think at this point manual intervention is required. Or was there >> > something else you were thinking it should do (because clearly you >> > were surprised, which isn't the intent). >> >> Well, I wasn't *too* surprised. I guess I was hoping for everything to >> work perfectly with no intervention. But it does seem to be working now, >> with a longer timeout. >> > > Some followup (#10702 notwithstanding): > > So I tried out the patchbot. Seemed to work reasonably well at > first. > > Then I came into my office this morning. Computer was humming at a > VERY decent clip; I could not get the screen to appear, Ctrl-C did > nothing, nothing nothing nothing, but clearly very busy (testing, > perhaps). I had to restart it manually. > > Now I'm looking for where the patchbot might have left some residue of > its doings so that I can make sure this doesn't happen again (perhaps > by setting some configuration thingie). But I can really only find > the local/bin/patchbot folder, which doesn't seem to have a log.
:(. There are log files in $SAGE_ROOT/logs/xxxx-log.txt . Still, it's just running sage -tp 3. > So I now have two questions: > > 1) Can I configure so that it runs ONE thread at a time? I noticed it > was running 3 threads... on a machine with one processor at < 1 GHz. > I didn't see a place for setting this in the patchbot - is that the > "parallelism": 3 setting? OK, that might explain it. Yes, set "parallelism": 1. And nice it of course as well. > Perhaps "doctest_threads" or something > could be an alternate setting. In any case, this should be a little > more sophisticated than 3 as a default - maybe number of cores +1 or > something. I hope this is what the problem I had was. Note that it's for building as well as doctesting, so I think "parallelism" is a fine name. Defaulting number of cores + 1 could be a bad default for a shared machine with lots of cores (and 2 may not be the best default for a 1-core machine). But, yes, it could be more intelligent. > 2) Is there a log? Or more precisely, is there one on *my* machine? Yep, see above. > 3) Finally, although http://patchbot.sagemath.org/ticket/ is pretty > nice, I couldn't find a way to do a query for what my particular > machine had tested. http://patchbot.sagemath.org/ticket/?base=4.8 > would be it, but that's pretty broad, and you have to click on a > ticket to see which machines did it. +1, I've wanted this too, but never got around to implementing it. (Should be easy.) Note that the tickets are sorted in "last activity" order. > Thanks! Overall this should be very helpful, though, especially for > checking whether things apply to more recent alphas/betas. Yep. People can run patchbots on a variety of architectures and versions of Sage. - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
