From: Jakub Narebski <jnareb@gmail.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: John 'Warthog9' Hawley <warthog9@kernel.org>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2010, #03; Wed, 24)
Date: Fri, 3 Dec 2010 14:02:48 +0100 [thread overview]
Message-ID: <201012031402.49169.jnareb@gmail.com> (raw)
In-Reply-To: <201012031222.33635.trast@student.ethz.ch>
On Fri, 3 Dec 2010, Thomas Rast wrote:
> Jakub Narebski wrote:
> > On Fri, 3 Dec 2010, Thomas Rast wrote:
> > > "gitweb: File based caching layer (from git.kernel.org)" does not work
> > > on my automated tester:
> [...]
> > 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
next prev parent reply other threads:[~2010-12-03 13:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 3:16 What's cooking in git.git (Nov 2010, #03; Wed, 24) Junio C Hamano
2010-11-25 3:42 ` Jiang Xin
2010-11-25 9:45 ` Ævar Arnfjörð Bjarmason
2010-11-25 10:35 ` Erik Faye-Lund
2010-11-25 12:00 ` Ævar Arnfjörð Bjarmason
2010-11-25 12:34 ` Erik Faye-Lund
2010-11-25 14:54 ` Erik Faye-Lund
2010-11-25 15:03 ` Erik Faye-Lund
2010-11-25 15:22 ` Erik Faye-Lund
2010-11-25 16:33 ` Ævar Arnfjörð Bjarmason
2010-11-25 17:55 ` Erik Faye-Lund
2010-11-25 18:06 ` Ævar Arnfjörð Bjarmason
2010-11-25 20:02 ` Erik Faye-Lund
2010-11-26 0:40 ` Ævar Arnfjörð Bjarmason
2010-11-25 10:41 ` Johannes Sixt
2010-11-25 16:26 ` Jakub Narebski
2010-12-03 10:36 ` Thomas Rast
2010-12-03 11:13 ` Jakub Narebski
2010-12-03 11:22 ` Thomas Rast
2010-12-03 13:02 ` Jakub Narebski [this message]
2010-12-03 13:06 ` Thomas Rast
2010-12-03 14:12 ` Jakub Narebski
2010-12-03 15:03 ` Thomas Rast
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201012031402.49169.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=trast@student.ethz.ch \
--cc=warthog9@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).