Subject: Re: What's cooking in git.git (Nov 2010, #03; Wed, 24)

From: Jakub Narebski <[email-masked]>
Date: Fri, 3 Dec 2010 12:13:05 +0100

On Fri, 3 Dec 2010, Thomas Rast wrote:
> Junio C Hamano wrote:
> > * jh/gitweb-caching (2010-11-01) 4 commits
> >  - gitweb: Minimal testing of gitweb caching
> >  - gitweb: File based caching layer (from git.kernel.org)
> >  - gitweb: add output buffering and associated functions
> >  - gitweb: Prepare for splitting gitweb
> 
> "gitweb: File based caching layer (from git.kernel.org)" does not work
> on my automated tester:
> 
>   ok 1 - setup
> 
>   expecting success: 
>           gitweb_run "p=.git;a=snapshot;h=$FULL_ID;sf=tar" &&
>           check_snapshot ".git-$SHORT_ID"
> 
>   basename=.git-1005c80
>   tar: This does not look like a tar archive
>   tar: Error exit delayed from previous errors
>   not ok - 2 snapshot: full sha1
>   #       
>   #               gitweb_run "p=.git;a=snapshot;h=$FULL_ID;sf=tar" &&
>   #               check_snapshot ".git-$SHORT_ID"
>   #       
> 
> Should I disable something with a Makefile option, or is that a bug?
> 
> (If you need more data you need to tell me what to look for, since I
> don't usually do gitweb.  The above is just the relevant snippet from
> 'make test' output).

What are the results of relevant part of

 $ cd t
 $ ./t9502-gitweb-standalone-parse-output.sh --debug

output?

Gitweb output caching should be turned off by default, so it shouldn't
affect tests before 'enable caching' test.
-- 
Jakub Narebski
Poland