From: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Implement timestamp'ed output on "make check"
Date: Thu, 06 Dec 2018 19:41:00 -0000 [thread overview]
Message-ID: <87o99yo33f.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <87efavbu02.fsf@redhat.com>
Sergio Durigan Junior <sergiodj@redhat.com> writes:
> I've now cancelled the builds; let's see how things go.
Thanks! The LE builder seem to be going faster now (a bit more than one
hour).
They still fail sometimes with a timeout for make. From the logs of the
ones that didn't fail it seems that gdb.threads/trace-condition.exp and
gdb.threads/tspeed.exp are the ones taking long, and could be causing
this, but I haven't looked into them yet.
--
Pedro Franco de Carvalho
prev parent reply other threads:[~2018-12-06 19:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 22:12 Sergio Durigan Junior
2018-11-23 14:42 ` Alan Hayward
2018-11-23 14:48 ` Sergio Durigan Junior
2018-11-23 15:03 ` [PATCH v2] " Sergio Durigan Junior
2018-11-23 18:23 ` Simon Marchi
2018-11-25 16:24 ` Sergio Durigan Junior
2018-11-25 19:56 ` Simon Marchi
2018-11-25 23:23 ` Sergio Durigan Junior
2018-11-26 0:47 ` Simon Marchi
2018-11-26 16:29 ` Sergio Durigan Junior
2018-11-26 17:22 ` Simon Marchi
2018-11-26 18:48 ` Sergio Durigan Junior
2018-12-05 19:39 ` [PATCH] " Pedro Franco de Carvalho
2018-12-05 19:48 ` Sergio Durigan Junior
2018-12-05 20:07 ` Pedro Franco de Carvalho
2018-12-05 20:26 ` Sergio Durigan Junior
2018-12-06 15:30 ` Pedro Alves
2018-12-06 15:54 ` Pedro Alves
2018-12-06 19:32 ` Pedro Franco de Carvalho
2018-12-06 19:52 ` Sergio Durigan Junior
2018-12-07 20:06 ` Pedro Alves
2018-12-07 22:09 ` Sergio Durigan Junior
2018-12-08 12:58 ` Pedro Alves
2018-12-08 23:16 ` Sergio Durigan Junior
2018-12-09 8:57 ` Philippe Waroquiers
2018-12-06 19:41 ` Pedro Franco de Carvalho [this message]
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=87o99yo33f.fsf@linux.vnet.ibm.com \
--to=pedromfc@linux.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.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.
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).