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 12:13:05 +0100 [thread overview]
Message-ID: <201012031213.06321.jnareb@gmail.com> (raw)
In-Reply-To: <201012031136.09156.trast@student.ethz.ch>
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
next prev parent reply other threads:[~2010-12-03 11:13 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 [this message]
2010-12-03 11:22 ` Thomas Rast
2010-12-03 13:02 ` Jakub Narebski
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=201012031213.06321.jnareb@gmail.com \
--to=jnareb@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=trast@student$(echo .)ethz.ch \
--cc=warthog9@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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