This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: MIPS build slave
- From: Brendan Kirby <brendan dot kirby at imgtec dot com>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>
- Cc: Simon Marchi <simon dot marchi at polymtl dot ca>, <gdb-patches at sourceware dot org>
- Date: Mon, 20 Jul 2015 18:50:34 -0700
- 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> <87fv4kswuh dot fsf at redhat dot com> <55AD543B dot 5010301 at imgtec dot com> <87fv4iczgm dot fsf at redhat dot com> <55AD8A7F dot 3080009 at imgtec dot com> <877fpu9xjh dot fsf at redhat dot com>
On 07/20/2015 05:14 PM, Sergio Durigan Junior wrote:
> On Monday, July 20 2015, Brendan Kirby wrote:
>
>> When I run it manually, it generates no output and it exits with 0. I'm
>> not sure what it's supposed to do, but if it's a test, I'm guessing the
>> test passed. Maybe it isn't passing in the Buildbot because of the
>> SHELL environment variable being set wrong like Simon suggested? I've
>> fixed the systemd service file to set the SHELL environment variable to
>> /bin/bash before starting the Buildbot slave. So, that problem should
>> be resolved now.
> Yeah, I think Simon hit the nail about the problem: if $SHELL is nologin
> GDB will get confused about things. In this case, the easier solution
> is to use /bin/{,ba}sh as the buildslave user's shell. Can you do that?
> You can still edit you /etc/ssh/sshd_config and disallow the buildslave
> there.
>
As I mentioned before, I've already made this change and restarted the
build slave. I'm seeing SHELL=/bin/bash in the environment for steps in
the currently running build. Let me know if this fixes things.
Brendan