Re: MIPS build slave

Sergio Durigan Junior
2015-07-20T21:05:01Z

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