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

Re: [PATCH 4/4] t4300 (rebase): don't unnecessarily set GIT_TRACE

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
May 11, 2013, 11:37 UTC
Message-ID
<CALkWK0=rqjduiWsj2-iqCoW9tsv4G8gvpf7fCZwg5=TKuEo+bA@mail.gmail.com>
In-Reply-To
<7vk3n6zgr3.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> But the output from passing "-v" before the test that breaks is not
> very useful for two reasons.

I sometimes checkout the Good branch in a different worktree, compare the output/ state of the passing test with the failing one. I've never really found the outputs from earlier tests enlightening. From my experience, the failure is often due to an earlier test not imposing tighter passing conditions: but because it's shell, the debugging time is very small. I always just patch-locally and run.

I'm not sure how to make the testing framework more useful.
Previous: Junio C HamanoNext: Jonathan Nieder
Message 20 of 21 in “Trivial cleanups to t3400 (rebase)”
  1. 0/4 Trivial cleanups to t3400 (rebase)Ramkumar Ramachandra, May 10, 2013
  2. 1/4 t3400 (rebase): don't set GIT_AUTHOR_{NAME,EMAIL}Ramkumar Ramachandra, May 10, 2013
  3. Eric SunshineMay 10, 2013
  4. Ramkumar RamachandraMay 10, 2013
  5. Junio C HamanoMay 10, 2013
  6. 2/4 t3400 (rebase): downcase a couple of test titlesRamkumar Ramachandra, May 10, 2013
  7. 3/4 t3400 (rebase): move lone statement into a testRamkumar Ramachandra, May 10, 2013
  8. 4/4 t4300 (rebase): don't unnecessarily set GIT_TRACERamkumar Ramachandra, May 10, 2013
  9. Junio C HamanoMay 10, 2013
  10. Ramkumar RamachandraMay 10, 2013
  11. Junio C HamanoMay 10, 2013
  12. Ramkumar RamachandraMay 10, 2013
  13. Junio C HamanoMay 10, 2013
  14. Ramkumar RamachandraMay 10, 2013
  15. Ramkumar RamachandraMay 10, 2013
  16. Jonathan NiederMay 10, 2013
  17. Ramkumar RamachandraMay 10, 2013
  18. Jonathan NiederMay 10, 2013
  19. Junio C HamanoMay 10, 2013
  20. Ramkumar RamachandraMay 11, 2013
  21. Jonathan NiederMay 13, 2013

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.