www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.ldc - buildbot for alternative architectures now online

reply Kai Nacke <kai redstar.de> writes:
Hi all!

LDC is usable on other architectures than x86/x86_64, too. But 
since we lacked a CI server we often created regressions without 
noticing.

To improve the situation I have created my own buildbot setup. 
Currently there are the following slaves available: armv7 
(IFC6410 board, Krait CPU, hardfloat), armv8 (Runabove cloud 
image), POWER8 (PowerLinux provided by OSU Open Source Lab). I 
hope to add a second POWER8 slave soon, too.
The slaves start a build as soon as a change on the ltsmaster, 
master or merge-2.071 branch is detected. The setup is still not 
perfect but it is sufficient to see that the armv7 build from 
ltsmaster is almost green. :-)

The UI can be reached at http://buildbot.ldc-developers.org/. (I 
still work on the configuration - expect still some instability. 
Alternate address is currently 
http://redstarbuildbot.mynetgear.com:12080/ in case the official 
address wn't work.)

Do you like to support LDC development on alternative targets? If 
you have a box which has enough resources to build LDC and you 
are willing to run your own build slave then I can add your build 
slave to the setup. :-)

Regards,
Kai
Apr 03 2016
next sibling parent kink <noone nowhere.com> writes:
Cool stuff, thanks Kai.
Apr 05 2016
prev sibling next sibling parent Seb <seb wilzba.ch> writes:
On Monday, 4 April 2016 at 05:54:36 UTC, Kai Nacke wrote:
 Hi all!

 LDC is usable on other architectures than x86/x86_64, too. But 
 since we lacked a CI server we often created regressions 
 without noticing.

 [...]
That looks really great. Would be nice to have that for the official repositories too!
Apr 07 2016
prev sibling next sibling parent Kai Nacke <kai redstar.de> writes:
On Monday, 4 April 2016 at 05:54:36 UTC, Kai Nacke wrote:
 Hi all!

 LDC is usable on other architectures than x86/x86_64, too. But 
 since we lacked a CI server we often created regressions 
 without noticing.

 To improve the situation I have created my own buildbot setup. 
 Currently there are the following slaves available: armv7 
 (IFC6410 board, Krait CPU, hardfloat), armv8 (Runabove cloud 
 image), POWER8 (PowerLinux provided by OSU Open Source Lab). I 
 hope to add a second POWER8 slave soon, too.
 The slaves start a build as soon as a change on the ltsmaster, 
 master or merge-2.071 branch is detected. The setup is still 
 not perfect but it is sufficient to see that the armv7 build 
 from ltsmaster is almost green. :-)

 The UI can be reached at http://buildbot.ldc-developers.org/. 
 (I still work on the configuration - expect still some 
 instability. Alternate address is currently 
 http://redstarbuildbot.mynetgear.com:12080/ in case the 
 official address wn't work.)

 Do you like to support LDC development on alternative targets? 
 If you have a box which has enough resources to build LDC and 
 you are willing to run your own build slave then I can add your 
 build slave to the setup. :-)

 Regards,
 Kai
I encountered some stability issues with my setup. I guess that this is a standard challenge with first setup of a CI server. I moved the master to a Scaleway C1 cloud server. The setup is still not complete and not all buildslaves are currently connected. But I hope to have it ready soon. Regards, Kai
Apr 19 2016
prev sibling parent Johan Engelen <j j.nl> writes:
On Monday, 4 April 2016 at 05:54:36 UTC, Kai Nacke wrote:
 Hi all!

 LDC is usable on other architectures than x86/x86_64, too. But 
 since we lacked a CI server we often created regressions 
 without noticing.

 To improve the situation I have created my own buildbot setup. 
 Currently there are the following slaves available: armv7 
 (IFC6410 board, Krait CPU, hardfloat), armv8 (Runabove cloud 
 image), POWER8 (PowerLinux provided by OSU Open Source Lab). I 
 hope to add a second POWER8 slave soon, too.
Some Lit-based tests depend on the target architecture, and only pass if LLVM can target X86. Do I have to add a Lit feature flag so that we can define per test whether they require a specific arch? (we can use `llvm-config --targets-built` to test what LLVM supports).
Apr 23 2016