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

Re: [ANNOUNCE] GIT 1.5.4-rc3

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 12, 2008, 07:34 UTC
Message-ID
<7vejcnwl85.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<200801120926.14307.ismail@pardus.org.tr>
Ismail Dönmez <ismail@pardus.org.tr> writes:
Show 38 quoted lines
> Saturday 12 January 2008 09:11:23 tarihinde Junio C Hamano şunları yazmıştı:
>> The third rc for the next feature release GIT 1.5.4 is available
>> at the usual places:
>>
>>   http://www.kernel.org/pub/software/scm/git/
>>
>>   git-1.5.4.rc3.tar.{gz,bz2}			(tarball)
>>   git-htmldocs-1.5.4.rc3.tar.{gz,bz2}		(preformatted docs)
>>   git-manpages-1.5.4.rc3.tar.{gz,bz2}		(preformatted docs)
>>   testing/git-*-1.5.4.rc3-1.$arch.rpm	(RPM)
>
> I am seeing new failures compared to rc2 :
>
> *** t9200-git-cvsexportcommit.sh ***
> * FAIL 1: New file
>         mkdir A B C D E F &&
>              echo hello1 >A/newfile1.txt &&
>              echo hello2 >B/newfile2.txt &&
>              cp ../test9200a.png C/newfile3.png &&
>              cp ../test9200a.png D/newfile4.png &&
>              git add A/newfile1.txt &&
>              git add B/newfile2.txt &&
>              git add C/newfile3.png &&
>              git add D/newfile4.png &&
>              git commit -a -m "Test: New file" &&
>              id=$(git rev-list --max-count=1 HEAD) &&
>              (cd "$CVSWORK" &&
>              git cvsexportcommit -c $id &&
>              check_entries A "newfile1.txt/1.1/" &&
>              check_entries B "newfile2.txt/1.1/" &&
>              check_entries C "newfile3.png/1.1/-kb" &&
>              check_entries D "newfile4.png/1.1/-kb" &&
>              diff A/newfile1.txt ../A/newfile1.txt &&
>              diff B/newfile2.txt ../B/newfile2.txt &&
>              diff C/newfile3.png ../C/newfile3.png &&
>              diff D/newfile4.png ../D/newfile4.png
>              )
> Ideas appreciated.

Often the first failure is the most interesting one. Running the test under sh -x like this:

	$ cd t
	$ sh t9200-git-cvsexportcommit.sh -i -v

and then looking at "trash" directory would tell you which one of the long sequence of commands failed, and further investigation can be made from there.

Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Previous: Ismail DönmezNext: Ismail Dönmez
Message 3 of 29 in “[ANNOUNCE] GIT 1.5.4-rc3”
  1. Junio C HamanoJan 12, 2008
  2. Ismail DönmezJan 12, 2008
  3. Junio C HamanoJan 12, 2008
  4. Ismail DönmezJan 12, 2008
  5. Junio C HamanoJan 12, 2008
  6. Jeff KingJan 12, 2008
  7. Jeff KingJan 12, 2008
  8. valgrind test script integrationJeff King, Jan 12, 2008
  9. Jeff KingJan 12, 2008
  10. Johannes SchindelinJan 12, 2008
  11. Jeff KingJan 12, 2008
  12. René ScharfeJan 12, 2008
  13. Ismail DönmezJan 12, 2008
  14. Johannes SchindelinJan 12, 2008
  15. Jeff KingJan 12, 2008
  16. Junio C HamanoJan 12, 2008
  17. Roger C. SoaresJan 12, 2008
  18. Junio C HamanoJan 12, 2008
  19. [ANNOUNCE] GIT 1.5.4-rc4Junio C Hamano, Jan 21, 2008
  20. [ANNOUNCE] GIT 1.5.4-rc5Junio C Hamano, Jan 28, 2008
  21. Jeff KingJan 28, 2008
  22. Gustaf HendebyJan 29, 2008
  23. Junio C HamanoJan 29, 2008
  24. Jeff KingJan 29, 2008
  25. Steffen ProhaskaJan 29, 2008
  26. Steffen ProhaskaJan 13, 2008
  27. Steffen ProhaskaJan 21, 2008
  28. Johannes SchindelinJan 22, 2008
  29. Steffen ProhaskaJan 22, 2008

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.