From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: ben.woosley@gmail.com, Junio C Hamano <gitster@pobox.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: make test Unexpected passes
Date: Fri, 22 Apr 2016 21:05:24 +0100 [thread overview]
Message-ID: <571A8404.5030200@ramsayjones.plus.com> (raw)
Hi Ben, Junio,
Tonight, the testsuite passed with a couple of 'unexpected passes', viz:
$ tail -17 ptest-out
[13:24:29]
All tests successful.
Test Summary Report
-------------------
t3421-rebase-topology-linear.sh (Wstat: 0 Tests: 76 Failed: 0)
TODO passed: 50, 54
t6036-recursive-corner-cases.sh (Wstat: 0 Tests: 22 Failed: 0)
TODO passed: 11
Files=746, Tests=13515, 445 wallclock secs ( 3.83 usr 0.61 sys + 52.78 cusr 27.89 csys = 85.11 CPU)
Result: PASS
make clean-except-prove-cache
make[2]: Entering directory `/home/ramsay/git/t'
rm -f -r 'trash directory'.* 'test-results'
rm -f -r valgrind/bin
make[2]: Leaving directory `/home/ramsay/git/t'
make[1]: Leaving directory `/home/ramsay/git/t'
$
In the first case, t3421-*.sh, git bisect fingered commit f32ec670
("git-rebase--merge: don't include absent parent as a base", 20-04-2016).
In the second case, t6036-*.sh, git bisect fingered commit b61f9d6e
("ll-merge: use a longer conflict marker for internal merge", 14-04-2016).
I won't have any time tonight to look into this any further (are these
false positives?), so I thought I would just make sure you were aware
of these 'unexpected passes'.
ATB,
Ramsay Jones
next reply other threads:[~2016-04-22 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 20:05 Ramsay Jones [this message]
2016-04-22 22:19 ` make test Unexpected passes Elijah Newren
2016-04-27 22:05 ` Junio C Hamano
2016-04-27 22:39 ` Elijah Newren
2016-04-22 23:16 ` Ben Woosley
2016-04-24 19:09 ` Junio C Hamano
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=571A8404.5030200@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=ben.woosley@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 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.