From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Brendan Kirby <brendan.kirby@imgtec.com>
Cc: Simon Marchi <simon.marchi@polymtl.ca>, <gdb-patches@sourceware.org>
Subject: Re: MIPS build slave
Date: Mon, 20 Jul 2015 21:05:00 -0000 [thread overview]
Message-ID: <87fv4iczgm.fsf@redhat.com> (raw)
In-Reply-To: <55AD543B.5010301@imgtec.com>
On Monday, July 20 2015, Brendan Kirby wrote:
> On 07/18/2015 07:30 PM, Sergio Durigan Junior wrote:
>> On Saturday, July 18 2015, Brendan Kirby wrote:
>>
>> Hi Brendan,
>>
>>> If I'm reading this right, it looks like it's trying to exec a file that
>>> doesn't exist. I think it's trying to exec:
>>> /mips/proj/build-compiler/upstream-testing/mipsswbrd048/GDB-testing/debian-mips-m64/build/gdb/testsuite/outputs/gdb.mi/mi-watch/mi-watch
>> This file should exist, because it was correctly compiled before during
>> the testcase run:
>>
>> Executing on host: gcc
>> ../../../binutils-gdb/gdb/testsuite/gdb.mi/basics.c -g -lm -o
>> /mips/proj/build-compiler/upstream-testing/mipsswbrd048/GDB-testing/debian-mips-m64/build/gdb/testsuite/outputs/gdb.mi/mi-watch/mi-watch
>> (timeout = 300)
>> spawn gcc ../../../binutils-gdb/gdb/testsuite/gdb.mi/basics.c -g -lm
>> -o
>> /mips/proj/build-compiler/upstream-testing/mipsswbrd048/GDB-testing/debian-mips-m64/build/gdb/testsuite/outputs/gdb.mi/mi-watch/mi-watch
> I ran the steps below. The build was successful. I built with commit
> 7ac018954bd9 because the latest one was failing to build. However, I'm
> still not seeing this file. I've attached the output of running "make
> check RUNTESTFLAGS='gdb.mi/mi-watch.exp'" in the file
> gdb.mi-mi-watch.exp.out and I've attached the gdb/testsuite/gdb.log file
> in gdb.mi-mi-watch.exp.log. Let me know if you want me to try
> anything else.
Sorry, my bad. The outputs/ directory will only be created/used when
you set the FORCE_PARALLEL=1 variable. Could you please try running
the same command that the BuildBot runs?
make -k check -j1 FORCE_PARALLEL=1
And seeing if there's anything strange happening?
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-07-20 21:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 4:15 Simon Marchi
2015-07-18 5:28 ` Brendan Kirby
2015-07-19 2:35 ` Sergio Durigan Junior
2015-07-20 20:04 ` Brendan Kirby
2015-07-20 20:45 ` Simon Marchi
2015-07-20 21:24 ` Brendan Kirby
2015-07-20 21:31 ` Simon Marchi
2015-07-20 21:05 ` Sergio Durigan Junior [this message]
[not found] ` <55AD8A7F.3080009@imgtec.com>
2015-07-21 0:14 ` Sergio Durigan Junior
2015-07-21 1:50 ` Brendan Kirby
2015-07-21 4:34 ` Sergio Durigan Junior
2015-07-21 14:57 ` Simon Marchi
2015-07-21 16:38 ` Brendan Kirby
2015-07-21 16:42 ` Simon Marchi
2015-07-21 17:21 ` Brendan Kirby
2015-07-21 17:43 ` Simon Marchi
2015-07-23 11:20 ` Pedro Alves
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=87fv4iczgm.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brendan.kirby@imgtec.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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