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: Tue, 21 Jul 2015 04:34:00 -0000 [thread overview]
Message-ID: <87380i9li6.fsf@redhat.com> (raw)
In-Reply-To: <55ADA56A.5090301@imgtec.com> (Brendan Kirby's message of "Mon, 20 Jul 2015 18:50:34 -0700")
On Monday, July 20 2015, Brendan Kirby wrote:
>> 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.
Sorry, I missed that message. Anyway, now the build is broken for MIPS,
so it's not reaching the testscase part. Let's wait until it gets
fixed.
Cheers,
--
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-21 4:34 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
[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 [this message]
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=87380i9li6.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