From: Pavel Roskin <proski@gnu.org>
To: Junio C Hamano <junio@siamese.dyndns.org>, git <git@vger.kernel.org>
Subject: cogito testsuite failure
Date: Tue, 31 May 2005 23:47:52 -0400 [thread overview]
Message-ID: <1117597672.13776.17.camel@dv> (raw)
Hello!
"make test" fails for current cogito:
*** t4008-diff-break-rewrite.sh ***
* ok 1: setup
* ok 2: change file1 with copy-edit of file0 and remove file0
* ok 3: run diff with -B
* ok 4: validate result of -B (#1)
* ok 5: run diff with -B and -M
* ok 6: validate result of -B -M (#2)
* ok 7: swap file0 and file1
* ok 8: run diff with -B
* ok 9: validate result of -B (#3)
* ok 10: run diff with -B and -M
* ok 11: validate result of -B -M (#4)
* ok 12: make file0 into something completely different
* ok 13: run diff with -B
* FAIL 14: validate result of -B (#5) compare_diff_raw current expected
* ok 15: run diff with -B
* FAIL 16: validate result of -B -M (#6) compare_diff_raw current expected
* ok 17: run diff with -M
* FAIL 18: validate result of -M (#7) compare_diff_raw current expected
* ok 19: file1 edited to look like file0 and file0 rename-edited to file2
* ok 20: run diff with -B
* ok 21: validate result of -B (#8)
* ok 22: run diff with -B -M
* ok 23: validate result of -B -M (#9)
* failed 3 among 23 test(s)
The failures happens because the test uses file ../README, which was
changed recently (and therefore, its checksum changed as well). Also,
this and several other tests refer to ../COPYING, which is going to
change as well (it has an old mailing address of FSF).
I suggest that we use separate test files. It would be great if those
files included text in several languages to test support for non-ASCII
symbols (maybe HELLO from emacs sources).
Or maybe we could use short files embedded in the scripts. Or maybe we
could use sed to take significant portions of GPL that don't include
Linus' foreword, any mailing addresses or "19" when it's used as two
first digits of a year.
--
Regards,
Pavel Roskin
next reply other threads:[~2005-06-01 3:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 3:47 Pavel Roskin [this message]
2005-06-01 4:27 ` cogito testsuite failure Junio C Hamano
2005-06-01 5:34 ` Pavel Roskin
2005-06-01 5:55 ` 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=1117597672.13776.17.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=junio@siamese.dyndns.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 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).