Re: MIPS build slave

Brendan Kirby
2015-07-18T05:28:46Z

Simon,

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

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/

If it helps, here's the contents of that directory:
total 196
-rw-r--r-- 1 buildbot buildbot 19273 Jul 17 21:57 config.log
-rwxr-xr-x 1 buildbot buildbot 29244 Jul 17 21:57 config.status
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.ada
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.arch
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.asm
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.base
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.btrace
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.cell
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.compile
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.cp
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.disasm
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.dlang
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.dwarf2
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.fortran
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.gdb
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.go
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.guile
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.java
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.linespec
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.mi
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.modula2
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.multi
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.objc
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.opencl
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.opt
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.pascal
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.perf
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.python
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.reverse
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.server
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.stabs
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.threads
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.trace
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 gdb.xml
drwxr-xr-x 2 buildbot buildbot 4096 Jul 17 21:57 lib
-rw-r--r-- 1 buildbot buildbot 10521 Jul 17 21:57 Makefile

I don't know what was supposed to have happened. So, let me know what
you want me to try.

Brendan

On 07/17/2015 09:14 PM, Simon Marchi wrote:
> Hi Brendan,
>
> TLDR: I think most of the tests don't run properly on the MIPS build
> slaves, check gdb.log for "Cannot exec".
>
> Long version:
>
> I am trying to clear an unexpected pass in mi-watch.exp (the test
> expects gdb to fail, but it seems to work fine). git tells me the
> xfail was added by commit 4a543da in 2007 and that it was added with
> the MIPS platform in mind:
> https://www.sourceware.org/ml/gdb-patches/2007-09/msg00151.html
>
> I would therefore like to see if the test passes correctly on the MIPS
> platform today before removing the xfail. Unfortunately, the test
> doesn't run on the buildbot.
>
> You can check the gdb.log here, search for mi-watch.exp (warning,
> that's a very big file):
> http://gdb-build.sergiodj.net/cgit/Debian-MIPS-m64/.git/plain/gdb.log
>
> Here is the important snippet (with messed up formatting since I'm
> using gmail, sorry):
>
> 220-exec-run
> &"Cannot exec /mips/proj/build-compiler/upstream-testing/mipsswbrd048/GDB-testing/debian-mips-m64/build/gdb/testsuite/outputs/gdb.mi/mi-watch/mi-watch
> -c exec /mips/proj/build-compiler/upstream-testing/mipsswbrd048/GDB-testing/debian-mips-m64/build/gdb/testsuite/outputs/gdb.mi/mi-watch/mi-watch
> .\n"
> &"Error: No such file or directory\n"
> =thread-group-started,id="i1",pid="30605"
> =thread-created,id="1",group-id="i1"
> =thread-exited,id="1",group-id="i1"
> =thread-group-exited,id="i1"
> 220^error,msg="During startup program exited with code 127."
> (gdb)
> ERROR: Unable to start target
>
> There are many other tests that have the same problem, which is why I
> suspect that the tests don't run as they should.
>
> Simon