From: Ken Brown <kbrown@cornell.edu>
To: "João Távora" <joaotavora@gmail.com>
Cc: Glenn Morris <rgm@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: master updated (5fdf4fc -> 67c3a3a)
Date: Mon, 1 Jul 2019 22:28:18 +0000 [thread overview]
Message-ID: <e16b85b7-6cef-b306-6b8c-f15f7f85a795@cornell.edu> (raw)
In-Reply-To: <CALDnm50=9L771E6RnUog6=KUE8-5FrT6w=SCvCuxm6SyvqehtA@mail.gmail.com>
On 3/28/2019 3:05 PM, João Távora wrote:
> On Thu, Mar 28, 2019 at 5:35 PM João Távora <joaotavora@gmail.com
> <mailto:joaotavora@gmail.com>> wrote:
>
> On Thu, Mar 28, 2019 at 7:35 AM Robert Pluim <rpluim@gmail.com
> <mailto:rpluim@gmail.com>> wrote:
>
> >>>>> On Wed, 27 Mar 2019 20:23:09 +0200, Dmitry Gutov
> <dgutov@yandex.ru <mailto:dgutov@yandex.ru>> said:
>
> Dmitry> On 27.03.2019 20:04, João Távora wrote:
> >> Two questions:
> >>
> >> 1) can I know exactly which of the two commits caused the
> >> problem in hydra.nixos.org <http://hydra.nixos.org>
> <http://hydra.nixos.org>? (Actually,
> >> I think it was 67c3a3 according to Robert's separate
> >> message, but in general is it possible on hydra.nixos?)
>
> Dmitry> https://emba.gnu.org/emacs/emacs/pipelines?page=2&scope=all
> Dmitry> says that it was indeed 67c3a3.
>
>
> Thanks Dmitry. As I understand there are now two CI systems checking
> Emacs but only one of them checks every commit (and that is the emba
> one). Does it also provide access to the `x-tests.log` files?
>
> As did my git bisect. gcc 7.3, FWIW. Ancient, I know :-)
>
>
> Thanks, it is indeed "worth" something, since problems have arisen due
> to different GCC versions before. And it's not a question of being ancient
> it's a question of that being valuable information.
>
> Anyway, the tests fail with GCC=8.2 as well: they passed on my local test
> run for some reason (probably an oversight with stale .elc on my part).
> I'm working on a fix: you can give me a couple of days or revert
> 67c3a3 if it's becoming too much of a nuisance.
>
>
> I've fixed the problem. For those interested, this had to do with failing
> to detect the "In file included from xxx.c" errors in the gcc output. Any
> number of such conditions for the same file should be posted as an error,
> but wasn't.
I can't find where your fix was ever pushed. Am I missing something?
Ken
next prev parent reply other threads:[~2019-07-01 22:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190325145632.633.72531@vcs0.savannah.gnu.org>
[not found] ` <20190325145634.E71A520535@vcs0.savannah.gnu.org>
2019-03-26 14:01 ` master 67c3a3a 2/2: Avoid occasional confusion of Flymake C/C++ backend Robert Pluim
2019-03-27 17:43 ` João Távora
2019-03-27 12:23 ` master updated (5fdf4fc -> 67c3a3a) Glenn Morris
2019-03-27 12:50 ` Robert Pluim
2019-03-27 18:04 ` João Távora
2019-03-27 18:23 ` Dmitry Gutov
2019-03-28 7:34 ` Robert Pluim
2019-03-28 17:35 ` João Távora
2019-03-28 19:05 ` João Távora
2019-07-01 22:28 ` Ken Brown [this message]
2019-07-01 22:40 ` João Távora
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=e16b85b7-6cef-b306-6b8c-f15f7f85a795@cornell.edu \
--to=kbrown@cornell.edu \
--cc=emacs-devel@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).