2010/11/5 Thomas Rast <trast@xxxxxxxxxxxxxxx>:
> * 950[012]: these are very strange.
>
> Running them interactively appears to work ok, so maybe it is some
> environment bug. ÂThey appear to be "can't happen" style failures
Can you rerun it with GIT_TRACE="$TRASH_DIRECTORY/trace" set on the
failed tests?
> though, since they all look like (this one is from 9502)
>
> ÂInitialized empty Git repository in /local/home/trast/git/t/trash directory.t9502-gitweb-standalone-parse-output/.git/
> Âexpecting success:
> Â Â Â Â Âtest_commit first foo &&
> Â Â Â Â Âgit branch xx/test &&
> Â Â Â Â ÂFULL_ID=$(git rev-parse --verify HEAD) &&
> Â Â Â Â ÂSHORT_ID=$(git rev-parse --verify --short=7 HEAD)
>
> Âfatal: This operation must be run in a work tree
> Ânot ok - 1 setup
This test is OK for me, although the next ones fail (pu db22585). How
do I debug gitweb.perl? t9502.2 shows
FULL_ID = 1005c80cc11c531d327b12195027cbbb4ff9e3cb
SHORT_ID = 1005c80
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: Exiting with failure status due to previous errors
not ok - 2 snapshot: full sha1
Not very helpful.
On t9500.1, I get
[Fri Nov 5 02:09:15 2010] gitweb.perl: Undefined subroutine
&main::cache_fetch called at
/home/pclouds/w/git/t/../gitweb/gitweb.perl line 1124.
Setting PERLLIB makes it work, but shouldn't the test script have done
that already?
--
Duy
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html