From: "Joachim Schmitz" <jojo@schmitz-digital.de>
To: git@vger.kernel.org
Subject: make test
Date: Mon, 15 Oct 2012 12:36:00 +0200 [thread overview]
Message-ID: <k5gov5$fe1$1@ger.gmane.org> (raw)
Hi folks
I'm trying to understand why certain tests in 'make test' fail. Here's the
first one
$ ../git --version
git version 1.8.0.rc2.5.g6b89306
$ GIT_TEST_CMP_USE_COPIED_CONTEXT=true ./t0000-basic.sh # our diff doesn't
understand -u
ok 1 - .git/objects should be empty after git init in an empty repo
...
ok 3 - success is reported like this
not ok 4 - pretend we have a known breakage # TODO known breakage
This is expected, right?
ok 5 - pretend we have fixed a known breakage (run in sub test-lib)
...
ok 11 - tests clean up after themselves
the next is not though? Why might it be failing, where to check?
not ok - 12 tests clean up even on failures
#
# mkdir failing-cleanup &&
# (
# cd failing-cleanup &&
#
# cat >failing-cleanup.sh <<-EOF &&
# #!/bin/sh
#
# test_description='Failing tests with cleanup commands'
#
# # Point to the t/test-lib.sh, which isn't in ../ as usual
# TEST_DIRECTORY="/home/jojo/git/git/t"
# . "$TEST_DIRECTORY"/test-lib.sh
#
# test_expect_success 'tests clean up even after a failure' '
# touch clean-after-failure &&
# test_when_finished rm clean-after-failure &&
# (exit 1)
# '
# test_expect_success 'failure to clean up causes the test to
fail' '
# test_when_finished "(exit 2)"
# '
# test_done
#
# EOF
#
# chmod +x failing-cleanup.sh &&
# test_must_fail ./failing-cleanup.sh >out 2>err &&
# ! test -s err &&
# ! test -f "trash
directory.failing-cleanup/clean-after-failure" &&
# sed -e 's/Z$//' -e 's/^> //' >expect <<-\EOF &&
# > not ok - 1 tests clean up even after a failure
# > # Z
# > # touch clean-after-failure &&
# > # test_when_finished rm clean-after-failure &&
# > # (exit 1)
# > # Z
# > not ok - 2 failure to clean up causes the test to fail
# > # Z
# > # test_when_finished "(exit 2)"
# > # Z
# > # failed 2 among 2 test(s)
# > 1..2
# EOF
# test_cmp expect out
# )
#
ok 13 - git update-index without --add should fail adding
...
ok 47 - very long name in the index handled sanely
# still have 1 known breakage(s)
# failed 1 among remaining 46 test(s)
1..47
Bye, Jojo
next reply other threads:[~2012-10-15 10:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 10:36 Joachim Schmitz [this message]
2012-10-15 10:53 ` make test Johannes Sixt
2012-10-15 11:00 ` Joachim Schmitz
2012-10-15 11:18 ` Johannes Sixt
2012-10-15 11:37 ` Joachim Schmitz
2012-10-15 11:52 ` Johannes Sixt
2012-10-15 11:58 ` Joachim Schmitz
2012-10-15 12:09 ` Johannes Sixt
2012-10-15 12:34 ` Andreas Schwab
2012-10-15 13:18 ` Joachim Schmitz
2012-10-17 8:30 ` Joachim Schmitz
2012-10-15 13:18 ` Joachim Schmitz
-- strict thread matches above, loose matches on Subject: below --
2012-10-22 14:19 Joachim Schmitz
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='k5gov5$fe1$1@ger.gmane.org' \
--to=jojo@schmitz-digital.de \
--cc=git@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.