From: Glenn Morris <rgm@gnu.org>
To: 26084@debbugs.gnu.org
Cc: Tino Calancha <tino.calancha@gmail.com>
Subject: bug#26084: closed (Re: bug#26084: 24.5; epatch save wrong backups in Git multipatches)
Date: Fri, 31 Mar 2017 18:54:43 -0400 [thread overview]
Message-ID: <etbmsh5a6k.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <handler.26084.D26084.149008498412423.notifdone@debbugs.gnu.org> (GNU bug Tracking System's message of "Tue, 21 Mar 2017 08:30:03 +0000")
FYI, the test for this has been failing on hydra since it was added.
Sadly Hydra is deleting build products very quickly at the moment,
but I managed to catch the latest coverage evaluation while it was in
progress. The not very informative failure message is:
Running 2 tests (2017-03-31 22:21:13+0000)
passed 1/2 ediff-ptch-test-bug25010
Test ediff-ptch-test-bug26084 backtrace:
(if (not (unwind-protect (setq value-17 (apply fn-15 args-16)) (setq
(let (form-description-19) (if (not (unwind-protect (setq value-17 (
(let ((value-17 (quote ert-form-evaluation-aborted-18))) (let (form-
(let ((fn-15 (function string=)) (args-16 (list (let ((temp-buffer (
(while --dolist-tail-- (setq x (car --dolist-tail--)) (let ((fn-15 (
(let ((--dolist-tail-- (list qux bar)) x) (while --dolist-tail-- (se
(let* ((info (progn (ediff-map-patch-buffer (current-buffer)) ediff-
(unwind-protect (let* ((info (progn (ediff-map-patch-buffer (current
(let* ((tmpdir (make-temp-file "ediff-ptch-test" t)) (default-direct
(lambda nil (let ((fn-5 (function executable-find)) (args-6 (list "g
ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
ert-run-test([cl-struct-ert-test ediff-ptch-test-bug26084 "Test for
ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test e
ert-run-tests(t #[385 "\306\307\"\203G\211\211G\310U\203\211@\20
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit(nil)
eval((ert-run-tests-batch-and-exit nil))
command-line-1(("-L" ":." "-l" "ert" "-l" "lisp/vc/ediff-ptch-tests.
command-line()
normal-top-level()
Test ediff-ptch-test-bug26084 condition:
(ert-test-failed
((should-not
(string=
(with-temp-buffer ... ...)
(with-temp-buffer ... ...)))
:form
(string= "foo here
" "foo here
")
:value t))
FAILED 2/2 ediff-ptch-test-bug26084
Ran 2 tests, 1 results as expected, 1 unexpected (2017-03-31 22:21:14+0000)
1 unexpected results:
FAILED ediff-ptch-test-bug26084
ERROR: lisp/vc/ediff-ptch-tests.log
next prev parent reply other threads:[~2017-03-31 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 14:24 bug#26084: 24.5; epatch save wrong backups in Git multipatches Tino Calancha
2017-03-21 8:29 ` Tino Calancha
[not found] ` <handler.26084.D26084.149008498412423.notifdone@debbugs.gnu.org>
2017-03-31 22:54 ` Glenn Morris [this message]
2017-04-01 3:33 ` bug#26084: closed (Re: bug#26084: 24.5; epatch save wrong backups in Git multipatches) Tino Calancha
2017-04-02 15:51 ` Glenn Morris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=etbmsh5a6k.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=26084@debbugs.gnu.org \
--cc=tino.calancha@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).