Re: What's cooking in git.git (Nov 2010, #03; Wed, 24)
From: Jakub Narebski <hidden>
Date: 2016-06-15 22:50:10
On Fri, 3 Dec 2010, Thomas Rast wrote:
Jakub Narebski wrote:quoted
On Fri, 3 Dec 2010, Thomas Rast wrote:
quoted
quoted
"gitweb: File based caching layer (from git.kernel.org)" does not work on my automated tester:[...]quoted
What are the results of relevant part of $ cd t $ ./t9502-gitweb-standalone-parse-output.sh --debug output?ok 1 - setup FULL_ID = 1005c80cc11c531d327b12195027cbbb4ff9e3cb SHORT_ID = 1005c80 not ok - 2 snapshot: full sha1 # # gitweb_run "p=.git;a=snapshot;h=$FULL_ID;sf=tar" && # check_snapshot ".git-$SHORT_ID" # Status: 200 OK Content-disposition: inline; filename=".git-1005c80.tar" Content-Type: application/x-tar They all fail after that, the rest of the output is at the end.
Could you add 'exit' just after second test in
t/t9502-gitweb-standalone-parse-output.sh test script, or running it
with `--immediate' option, and show us the results (after 'cd t') of
$ file "trash directory.t9502-gitweb-standalone-parse-output/gitweb.body"
should be:
trash directory.t9502-gitweb-standalone-parse-output/gitweb.body: tar archive
$ grep '<head>' "trash directory.t9502-gitweb-standalone-parse-output/gitweb.body"
should be empty
$ du -b "trash directory.t9502-gitweb-standalone-parse-output/gitweb.body"
should be:
10240 trash directory.t9502-gitweb-standalone-parse-output/gitweb.body
OTOH if I check out v1.7.3.1-48-g5768176 instead, where the test works ok, it looks like this: [...]
Could you bisect to commit that introduces breakage? Thanks in advance. -- Jakub Narebski Poland