|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#32764: closed (Some flymake tests seem unstable) |
Date: | Sun, 06 Jan 2019 19:03:02 +0000 |
Your message dated Sun, 6 Jan 2019 19:01:47 +0000 with message-id <address@hidden> and subject line Re: bug#32764: Some flymake tests seem unstable has caused the debbugs.gnu.org bug report #32764, regarding Some flymake tests seem unstable to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 32764: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=32764 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: Somne flymake tests seem unstable Date: Tue, 18 Sep 2018 14:17:53 -0400 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) Package: emacs Version: 27.0.50 Severity: minor Ref: https://hydra.nixos.org/build/81615914 I've seen some flymake test failures like the following a few times. Perhaps some timeout needs to be increased. Test included-c-header-files condition: (ert-test-failed "Some backends not reporting yet (flymake-cc)") FAILED 4/9 included-c-header-files (10.545006 sec) Test perl-backend condition: (error "Selecting deleted buffer") FAILED 5/9 perl-backend (0.289559 sec) Test recurrent-backend condition: (error "Selecting deleted buffer") FAILED 6/9 recurrent-backend (0.005780 sec) Test warning-predicate-function-gcc condition: (ert-test-failed "Some backends not reporting yet (flymake-cc)") FAILED 8/9 warning-predicate-function-gcc (5.444343 sec)
--- End Message ---
--- Begin Message ---Subject: Re: bug#32764: Some flymake tests seem unstable Date: Sun, 6 Jan 2019 19:01:47 +0000 I guess we can close this bug, then.JoãoOn Sun, Jan 6, 2019, 01:20 Paul Eggert <address@hidden wrote:João Távora wrote:
> Hi Paul, this test failure is compatible with a problem with GCC 8.2
> that I recently fixed in 04d3315271cd1357fbbc192505d00c760be02952. Can
> you check if your compiler's version? If it doesn't report the column
> for "In file included from" errors, it would have triggered the failure
> before my fix.
It's gcc (GCC) 8.2.1 20181215 (Red Hat 8.2.1-6).
I'm not observing the error now; thanks.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |