From: Linus Torvalds <torvalds@linux-foundation.org>
To: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Lea Wiemann <LeWiemann@gmail.com>
Subject: perl t9700 failures?
Date: Sun, 29 Jun 2008 12:52:00 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0806291241210.27776@hp.linux-foundation.org> (raw)
Am I the only one who gets this error:
*** t9700-perl-git.sh ***
* ok 1: set up test repository
* run 2: Perl API (perl ../t9700/test.pl)
* FAIL 2: Perl API
perl ../t9700/test.pl
* FAIL 3: no stderr: Perl API
perl ../t9700/test.pl
* failed 2 among 3 test(s)
which I have no idea about, since to me perl is a black box, and doing
run of the tests with '-i -v' doesn't actually tell any more about which
part of the perl script is failing, or why.. Trying to run the perl thing
by hand, though, gives me this:
Can't locate Test/More.pm in @INC (@INC contains: ...)
which is presumably the problem. It looks like it is assuming I have the
Test::More perl libs, which I presumably don't have, don't have any clue
where they are, nor really any interest in installing.
Wouldn't it be a lot more polite to just not run the test when the
Test::More stuff doesn't exist? Rather than failing the testsuite? From a
quick "git grep", this test is the only one that uses Test::More..
Linus
next reply other threads:[~2008-06-29 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 19:52 Linus Torvalds [this message]
2008-06-29 20:18 ` perl t9700 failures? Junio C Hamano
2008-06-30 1:17 ` Linus Torvalds
2008-06-29 20:23 ` Junio C Hamano
2008-06-29 22:53 ` Jakub Narebski
2008-06-29 22:56 ` Lea Wiemann
2008-06-30 6:11 ` Johannes Sixt
2008-06-29 20:32 ` [PATCH] Skip Perl interface (Git.pm) tests if requirements not fullfilled Jakub Narebski
2008-06-29 21:55 ` perl t9700 failures? Johannes Schindelin
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=alpine.LFD.1.10.0806291241210.27776@hp.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=LeWiemann@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).