On Sun, Oct 22, 2017 at 5:36 PM, Jeff King <peff@xxxxxxxx> wrote: > On Sun, Oct 22, 2017 at 07:54:57PM +0530, Kaartic Sivaraam wrote: > >> On Fri, 2017-10-20 at 13:45 -0700, Stefan Beller wrote: >> > >> > The git-test from Michael sounds intriguing. Initially I put off using >> > it as I had my main working dir (or rather test dir) on a spinning >> > disk, still. Now I test in memory only, which is a lot faster, so I could >> > try if git-test can keep up with my local commit pace. >> > >> >> Excuse my ignorance but I don't get your statement correctly. What do >> you mean by "I test in memory only"? How do you do that? > > I assume it means pointing "--root" at a tmpfs or ram disk in > GIT_TEST_OPTS. That makes the test suite run _way_ faster. Exactly. By memory I mean volatile RAM (as opposed to memory on a spinning disk). Using GIT_TEST_OPTS has had some issues (I remember vaguely there was an inconsistency between the output of `make test` and prove), so I put my entire working tree on a tmpfs, I run roughly this script after booting my computer: sudo mount -t tmpfs -o size=16g tmpfs /u mkdir /u/git echo "gitdir: /usr/local/google/home/sbeller/OSS/git/.git/worktrees/git" >/u/git/.git git -C /u/git checkout -f HEAD cat <<EOF >/u/config.mak DEVELOPER=1 DEVELOPERS=1 CFLAGS += -g -O2 CFLAGS += -DFLEX_ARRAY=2048 #CFLAGS += -Wno-unused-value EOF The downside (or upside?) is that there will be no files cluttering my git directory, but any untracked file is wiped periodically. So if I want to really preserve a thing I am forcing myself to put it somewhere else than in an untracked file inside the git repo. The test suite (excluding t9*) runs in less than 50 seconds on the ram disk. Thanks, Stefan > > -Peff
