This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: MIPS build slave
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Brendan Kirby <brendan dot kirby at imgtec dot com>
- Cc: Simon Marchi <simon dot marchi at polymtl dot ca>, <gdb-patches at sourceware dot org>
- Date: Sat, 18 Jul 2015 22:30:14 -0400
- Subject: Re: MIPS build slave
- Authentication-results: sourceware.org; auth=none
- References: <CAFXXi0n=5hwk0JE82gz_QEytsU0P36=4AbNdj_1wt1zmph28bw at mail dot gmail dot com> <55A9E3F5 dot 3090902 at imgtec dot com>
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
> In fact, I'm not seeing any of the sub-directories either. The first
> directory I'm seeing is:
> /mips/proj/build-compiler/upstream-testing/mipsswbrd048/GDB-testing/debian-mips-m64/build/gdb/testsuite/
The debian-mips-m64 directory gets removed on every build, so depending
on when you examine it you won't find the testsuite results there.
My first advice would be to replicate what the BuildBot does to compile
GDB, but on a temporary directory outside the buildslave's dir (so that
you won't affect existing builds). Feel free to stop your buildslave
while doing the steps below, if you are afraid it's going to be too much
for the poor hardware.
For example, you can do:
../binutils-gdb/configure --disable-binutils --disable-ld --disable-gold \
--disable-gas --disable-sim --disable-gprof --enable-targets=all --with-separate-debug-dir=/usr/lib/debug
make -j1 all
make -k check -j1 FORCE_PARALLEL=1 # see below before typing this
Running the entire testsuite may be too much, so you can run only one
test by doing:
make check RUNTESTFLAGS='gdb.mi/mi-watch.exp'
That should give you/us some clues about what's going on.
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/