From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: "João Távora" <joaotavora@gmail.com>, 32764@debbugs.gnu.org
Subject: bug#32764: Some flymake tests seem unstable
Date: Wed, 19 Sep 2018 21:09:08 -0700 [thread overview]
Message-ID: <a52f1aa7-86cf-cf12-d112-631850128f31@cs.ucla.edu> (raw)
In-Reply-To: <yqo9cuy8j2.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 168 bytes --]
For what it's worth, the flymake tests typically fail for me on master. I
normally test on Fedora 28 x86-64 on a circa-2010 AMD Phenom II X4 910e. Log
file attached.
[-- Attachment #2: flymake-tests.log --]
[-- Type: text/x-log, Size: 1947 bytes --]
Running 9 tests (2018-09-19 21:06:16-0700, selector `(not (or (tag :expensive-test) (tag :unstable)))')
Test different-diagnostic-types backtrace:
signal(ert-test-failed (((should (eq 'flymake-error (face-at-point))
ert-fail(((should (eq 'flymake-error (face-at-point))) :form (eq fly
#f(compiled-function () #<bytecode 0x513fe9>)()
flymake-tests--call-with-fixture(#f(compiled-function () #<bytecode
#f(compiled-function () #<bytecode 0x5143d1>)()
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name different-diagnostic-types :documenta
ert-run-or-rerun-test(#s(ert--stats :selector (not (or ... ...)) :te
ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
command-line-1(("-L" ":." "-l" "ert" "-l" "lisp/progmodes/flymake-te
command-line()
normal-top-level()
Test different-diagnostic-types condition:
(ert-test-failed
((should
(eq 'flymake-error
(face-at-point)))
:form
(eq flymake-error flymake-note)
:value nil))
FAILED 1/9 different-diagnostic-types (1.170822 sec)
passed 2/9 dummy-backends (1.003490 sec)
passed 3/9 eob-region-and-trailing-newline (0.000554 sec)
passed 4/9 included-c-header-files (2.058290 sec)
passed 5/9 perl-backend (1.037708 sec)
passed 6/9 recurrent-backend (1.002835 sec)
skipped 7/9 ruby-backend (0.000520 sec)
passed 8/9 warning-predicate-function-gcc (1.027205 sec)
passed 9/9 warning-predicate-rx-gcc (1.044844 sec)
Ran 9 tests, 7 results as expected, 1 unexpected, 1 skipped (2018-09-19 21:06:25-0700, 8.515835 sec)
1 unexpected results:
FAILED different-diagnostic-types
1 skipped results:
SKIPPED ruby-backend
next prev parent reply other threads:[~2018-09-20 4:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 18:17 bug#32764: Somne flymake tests seem unstable Glenn Morris
2018-09-19 17:55 ` João Távora
2018-09-20 4:09 ` Paul Eggert [this message]
2019-01-05 11:56 ` bug#32764: Some " João Távora
2019-01-06 1:20 ` Paul Eggert
2019-01-06 19:01 ` João Távora
2019-01-06 19:20 ` Glenn Morris
2019-01-06 22:41 ` João Távora
2019-01-08 1:40 ` 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=a52f1aa7-86cf-cf12-d112-631850128f31@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=32764@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=rgm@gnu.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.
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).