[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7vejcnwl85.fsf@gitster.siamese.dyndns.org>
Date: Fri, 11 Jan 2008 23:34:34 -0800
From: Junio C Hamano <gitster@...ox.com>
To: Ismail Dönmez <ismail@...dus.org.tr>
Cc: git@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.4-rc3
Ismail Dönmez <ismail@...dus.org.tr> writes:
> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists