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

Re: GIT+CYGWIN annoying test failure

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 24, 2007, 09:53 UTC
Message-ID
<Pine.LNX.4.63.0701241041190.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<45B6C1FB.7060005@gmail.com>
Hi,
On Wed, 24 Jan 2007, SungHyun Nam wrote:
Show 14 quoted lines
> First of all, this problem always existed to me. I was lazy to report. 
> Please check the failure logs and my GIT build script below. [...] the 
> first test failed at 't1000-read-tree-m-3way.sh' always. And in this 
> case, 2nd test always succeeded.
> 
> * FAIL 57: 5 - must match in !O && A && B && A==B case.
>         rm -f .git/index LL &&
>              cp .orig-A/LL LL &&
>              git-update-index --add LL &&
>              echo extra >>LL &&
>              git-read-tree -m 3fe085e0589de4327971d50e416fc292dd00fbfe
> 997bbc4a0a51e0574168a4f637739380edebe4d7
> 76d47d681d7f1d4fa975334a9a0ba8a6eeea2226 &&
>              check_result
It is not directly apparent what is causing this error. Could you please 
change your script to use "-i -v" on the tests? I.e. instead of:
	
> 	    if ! make test
this:
	    if ! (cd t; GIT_TEST_OPTS="-i -v" make)

It should give us a better idea what happened, since we also see the error messages of the git commands.

If it is still not apparent what went wrong, there is unfortunately no way around doing that particular test case manually, as to find out what went wrong. Since you seem to be the only one who can reproduce this bug, it boils down to you having to do the leg work.

Please keep us posted!

Ciao, Dscho

Previous: SungHyun NamNext: SungHyun Nam
Message 2 of 9 in “GIT+CYGWIN annoying test failure”
  1. SungHyun NamJan 24, 2007
  2. Johannes SchindelinJan 24, 2007
  3. SungHyun NamJan 29, 2007
  4. Johannes SchindelinFeb 1, 2007
  5. SungHyun NamFeb 2, 2007
  6. SungHyun NamFeb 15, 2007
  7. Johannes SchindelinFeb 15, 2007
  8. SungHyun NamFeb 16, 2007
  9. Junio C HamanoFeb 16, 2007

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.