git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Jul 2021, #03; Tue, 13)

From
Jeff King <peff@peff.net>
Date
Jul 19, 2021, 10:52 UTC
Message-ID
<YPVZcA2z9cmTe5D5@coredump.intra.peff.net>
In-Reply-To
<YPVW50Q6oyTxQ4D4@ncase>
On Mon, Jul 19, 2021 at 12:41:43PM +0200, Patrick Steinhardt wrote:
Show 22 quoted lines
> > TBH, I had never really considered using TEST_OUTPUT_DIRECTORY for this
> > (--root predates it, and was written explicitly for the tmpfs case). But
> > I also think --root is more convenient:
> > 
> >   - "make test" will run in the tmpfs for speed, but "./t1234-foo.sh -i"
> >     will run locally, which makes it easy to "cd" in to inspect the
> >     result
> > 
> >   - likewise, I find accessing the results in t/test-results/*.out a
> >     little more convenient
> > 
> > But all of that is preference. I don't think you're wrong to use
> > TEST_OUTPUT_DIRECTORY this way, but the above points might be
> > interesting to you.
> 
> It is, thanks a lot for the hint. But given your first point about
> direct execution, this in fact makes me want TEST_OUTPUT_DIRECTORY in
> contrast to `--root=/path/to/tmpfs`: especially in the context of perf
> tests, I never run all of them together given that it takes such a long
> time. So I instead either run them directly or via the `./run` script,
> and in both cases I definitely want to have them in tmpfs given that
> there's a lot of disk churn if you're using biggish repos.

I generally use "./run", too. It will use GIT_TEST_OPTS under the hood (which I actually find a little odd, just because it kicks in my usual "-x --verbose-log", which I don't actually care about for the perf tests).

You'd have to specify it manually for single-script runs, though. I usually avoid single-script runs (and instead use "./run") because I try to make sure each run is associated with a commit. Otherwise, it's easy to confuse yourself about what the state of "this tree" was when it ran (it does not even build fresh with GIT_PERF_MAKE_OPTS! So many times I've accidentally tested a -O0 build from the current tree and wondered why it was so slow).

-Peff
Previous: Patrick SteinhardtNext: Junio C Hamano
Message 35 of 43 in “What's cooking in git.git (Jul 2021, #03; Tue, 13)”
  1. Junio C HamanoJul 14, 2021
  2. Eric SunshineJul 14, 2021
  3. Junio C HamanoJul 14, 2021
  4. Eric SunshineJul 14, 2021
  5. Junio C HamanoJul 14, 2021
  6. Han-Wen NienhuysJul 14, 2021
  7. Ævar Arnfjörð BjarmasonJul 14, 2021
  8. Ævar Arnfjörð BjarmasonJul 14, 2021
  9. Junio C HamanoJul 14, 2021
  10. Derrick StoleeJul 14, 2021
  11. Ævar Arnfjörð BjarmasonJul 14, 2021
  12. CodingGuidelines: recommend gender-neutral descriptionJunio C Hamano, Jul 15, 2021
  13. Eric SunshineJul 15, 2021
  14. Taylor BlauJul 15, 2021
  15. Junio C HamanoJul 15, 2021
  16. Felipe ContrerasJul 16, 2021
  17. Derrick StoleeJul 15, 2021
  18. Johannes SchindelinJul 16, 2021
  19. Felipe ContrerasJul 16, 2021
  20. CodingGuidelines: recommend gender-neutral descriptionJunio C Hamano, Jul 16, 2021
  21. Derrick StoleeJul 16, 2021
  22. Ævar Arnfjörð BjarmasonJul 16, 2021
  23. Junio C HamanoJul 16, 2021
  24. Felipe ContrerasJul 16, 2021
  25. Bagas SanjayaAug 12, 2021
  26. Taylor BlauJul 14, 2021
  27. Patrick SteinhardtJul 19, 2021
  28. Felipe ContrerasJul 19, 2021
  29. Jeff KingJul 19, 2021
  30. Felipe ContrerasJul 19, 2021
  31. Patrick SteinhardtJul 19, 2021
  32. Felipe ContrerasJul 19, 2021
  33. Jeff KingJul 19, 2021
  34. Patrick SteinhardtJul 19, 2021
  35. Jeff KingJul 19, 2021
  36. Junio C HamanoJul 19, 2021
  37. Felipe ContrerasJul 19, 2021
  38. Patrick SteinhardtJul 20, 2021
  39. Felipe ContrerasJul 20, 2021
  40. t0000: fix test if run with TEST_OUTPUT_DIRECTORYPatrick Steinhardt, Jul 20, 2021
  41. Jeff KingJul 20, 2021
  42. Junio C HamanoJul 20, 2021
  43. Felipe ContrerasJul 20, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.