On Mon, May 5, 2014 at 7:47 AM, William Stein <wst...@gmail.com> wrote: > On Mon, May 5, 2014 at 7:10 AM, Ralf Stephan <gtrw...@gmail.com> wrote: >> Hello, >> please bear with me and give me a hint why ... >> >> 1. isn't make just doing sage -b whenever nothing in >> lib/ is changed (or any suitable definition of lib)? >> A counterexample would suffice. >> >> 2. why does patchbot make and test twice per ticket, even with skip-base?
It shouldn't, why are you seeing this? >> i.e., is it not worthwhile to make/test base, snapshot, make/test >> ticket #1, reload snapshot, make/test ticket #2...? >> With snapshot I mean an equivalent of cp -dpR / rsync / tar. I'd welcome such an option. > Quick question -- would patchbot benefit a lot from using a filesystem > (e.g., ZFS) that has lightweight snapshot+clones? With ZFS you can > make a snapshot of a point of time, then a read/write clone of it, and > just > start using it -- in a few seconds; when done, you can just destroy > it, which is also very quick. Yes, that could be nice, but not very platform independent. >> Unrelated: I am not convinced about ccache as a better solution >> because that needs 4Gb as well but hit rates are poor. ccache is much better than no ccache (I see decent hit rates), and 4Gb is *cheap*. Maybe we should increase that to 8 or 16Gb. >> 3. why not show the sage version the ticket was based and tested on >> by patchbot on the trac blob? What reason is there to show "6.1.1" >> when the ticket was tested by patchbots both a) by merging a develop >> version into 6.1.1 (so it's develop anyway) and b) based on current >> develop. Yes, this could be improved. We need a well defined difinition of "the sage version the ticket was based and tested on", maybe the latest version-like tag in its commit tree? - Robert -- 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.
