Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Peter Schauer <peterschauer@gmx.net>,
	       Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>,
	gdb-patches@sourceware.org,
	       Brendan Kirby <brendan.kirby@imgtec.com>
Subject: Re: [PATCH obv/pushed] MIPS ptrace build fixes
Date: Mon, 24 Aug 2015 14:48:00 -0000	[thread overview]
Message-ID: <55DB2EA1.800@redhat.com> (raw)
In-Reply-To: <201507300913.t6U9Dkio003773@licht.localdomain>

Hi guys,

The MIPS build slave continues showing random build failures,
which results in spurious and confusing "you broke gdb" nag emails.

We should at least disable email reports for this build
slave until this is sorted out.

On 07/30/2015 10:13 AM, Peter Schauer wrote:
>> On Wednesday, July 29 2015, Pedro Alves wrote:
>>>
>>>  http://gdb-build.sergiodj.net/builders/Debian-MIPS-m64/builds/77/steps/compile%20gdb/logs/stdio
>>>
>>> it shows the build had failed for an unrelated issue:
>>>
> This looks like a memory problem on the build slave, it seems that
> memory flipped from 0x73 ('s') to 0x63 ('c').

OOC, how did you figure this out?

Thanks,
Pedro Alves


  reply	other threads:[~2015-08-24 14:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 21:19 Simon Marchi
2015-07-29 21:26 ` Simon Marchi
2015-07-29 21:59   ` Pedro Alves
2015-07-29 22:32     ` Sergio Durigan Junior
2015-07-30  9:14       ` Peter Schauer
2015-08-24 14:48         ` Pedro Alves [this message]
2015-08-24 14:59           ` Peter Schauer
2015-08-24 15:03             ` Pedro Alves
2015-08-24 17:52               ` Brendan Kirby
2015-08-24 18:04                 ` Pedro Alves
2015-08-24 18:10                   ` Sergio Durigan Junior
2015-08-24 18:17                     ` Pedro Alves
2015-08-24 18:20                       ` Sergio Durigan Junior
2015-08-24 18:24                         ` Sergio Durigan Junior
2015-08-24 18:30                           ` Brendan Kirby
2015-08-24 18:05                 ` Sergio Durigan Junior

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=55DB2EA1.800@redhat.com \
    --to=palves@redhat.com \
    --cc=brendan.kirby@imgtec.com \
    --cc=gdb-patches@sourceware.org \
    --cc=peterschauer@gmx.net \
    --cc=sergiodj@redhat.com \
    --cc=simon.marchi@ericsson.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