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

Question re testing configuration

From
Samuel Lijin <sxlijin@gmail.com>
Date
Apr 27, 2017, 03:56 UTC
Message-ID
<CAJZjrdWPezo6=JHcp9mp8C5Pm1uJodSj3Mbgn7ix78MAqpUUXw@mail.gmail.com>
Hi all,

I'm a new developer trying to get my feet wet and I'm running into an issue with the tests that I can't figure out at this point.

I *know* that the changes I'm working on are causing the tests to fail, but I can't figure out how to induce the failure manually (so that I can throw gdb at the problem).

Specifically I'm seeing t5000-tar-tree.sh fail (as a result of adding extra diff_populate_filespec() calls before the estimate_similarity() loop in diffcore_rename()) on #52 "set up repository with huge blob" and #55 "set up repository with far-future commit".

If I run the commands fed into test_expect_success in t5000, though (in an empty repo initialized with git init), making sure to use the binary compiled with the breaking changes, the command doesn't fail, so I'm clearly missing something in the testing environment setup when I try to manually reproduce it.

Can someone point me in the right direction? I've spent some time now going through t/test-lib.sh and I haven't figured it out yet.

Thanks, Sam

Next: Jeff King
Message 1 of 2 in “Question re testing configuration”
  1. Samuel LijinApr 27, 2017
  2. Jeff KingApr 27, 2017

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.