This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Status of the AArch* builders


On Thursday, October 11 2018, Alan Hayward wrote:

>> On 24 Sep 2018, at 15:39, Sergio Durigan Junior <sergiodj@redhat.com> wrote:
>> 
>> On Monday, September 24 2018, Alan Hayward wrote:
>> 
>>>> On 20 Sep 2018, at 22:15, Sergio Durigan Junior <sergiodj@redhat.com> wrote:
>>>> Hi guys,
>>>> 
>>>> Just a ping to see if you have progressed on this.  I've left the AArch*
>>>> builders there, and now they're *really* behind (more than 1000 builds
>>>> in the queue), and at least one of the buildslaves is offline.
>>>> 
>>>> I will temporarily remove the builders now, but it would be really nice
>>>> to keep having AArch* builders in our BuildBot.
>>>> 
>>>> Thanks a lot,
>>> 
>>> 
>>> Ramana has got some aarch64 machines up on packet.net for use in buildbot instead
>>> of the existing machines. I think a few things just need finalising before they can
>>> be handed over.
>> 
>> That's great news.  Thanks for doing that.
>> 
>>> Once that’s done I can get buildbot set up on them. Are there some simple instructions
>>> for getting this going?
>> 
>> There are instructions on our wiki:
>> 
>>  https://sourceware.org/gdb/wiki/BuildBot#How_to_add_your_buildslave
>> 
>> But please do let me know if you need any help.  I can take care of the
>> configuration on my side, so you don't have to submit a patch for the
>> master.cfg file (although you can if you want).
>> 
>
> The machine is now ready for buildbot!
>
> Aarch64, Ubuntu 16.04.5 LTS, 96 cores

That's great news, Alan!

> I’ve setup buildbot-slave-0.8.14 in a virtualenv/
> (Oddly, I had to install twisted==16.4.1, as anything newer than that caused a hang).
>
> I’ve manually checked you can build gdb and run the testsuite.
>
> My recent experiments with the testsuite on Aarch64 show all the threaded tests
> are quite racy on a fully loaded ubuntu, whereas on redhat/suse they are fairly
> stable. I’m still looking into why this is. But, in the short-term maybe we should
> restrict the number of jobs to 32 (or maybe even fewer?)

Sure, no problem.  What do you think of 16?

> Sergio, could you please add the relevant server config.

It's a good idea to follow the instructions here:

  <https://sourceware.org/gdb/wiki/BuildBot#Buildslave_configuration>

And make sure that all of the necessary/recommended deps are installed
in the machine.  The more deps, the more tests will be performed.

You will need a password to connect to the BuildBot master.  I will send
it to you in private.

I also recommend creating at least 3 builders associated with each
slave: native, native-gdbserver, and native-extended-gdbserver.  If
you're OK with it, I'll do that.

Last question: is there any special flags needed to build GDB on the
machine?

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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]