[GSoC 2016] Testing strace on multiple distro/architecture

[Philippe Ombredanne]

On Wed, Mar 9, 2016 at 3:24 AM, 陳耘志 <cba840910 at gmail.com> wrote:
> Hello strace-developers:
>
>     My name is Yun-Chih Chen.  I'm a Computer Science sophomore from
> National Taiwan University.  As a system administration TA in our
> department, I frequently use strace for debugging in our workstations.
> I am eager to join the strace community and contribute as much as I
> can do.  I'm interested in the "Multi-OS and multiarch continuous
> tests infrastructure" idea and has been investigating solutions.
>     As suggested in this blog post [ http://goo.gl/Ddeg2G ], it might
> be a good idea to combine Travis CI and qemu to emulate different
> architecture.  openSUSE build service also adopts qemu for emulation (
> as seen in this doc: https://goo.gl/SBbP1Z ] and might give us more
> flexibility in terms of running time.  As for testing on different
> Linux Distro, Travis CI + Docker seems like a nice native solution.
>     It seems that Open Build Service requires us to set up an
> independent Linux box.  Conversely, Travis CI gives us an existing box
> so that we only need to write scripts.  Does that mean we need
> to"rent" a server in order to run OBS?  This does not seem like a good
> idea.  Or create our own catridge on Openshift?  Any advice on this
> topic?  Thanks in advance!!
>
>
> Yun-Chih Chen

Hi there! and thank you for considering strace for your GSOC applications.
Combining travis and qemu would be a great start I think.
Dmitry has already added an initial travis config here [1] . Check
this out as a base.
Docker in Travis would be quite interesting too.
Alternative could include drone.io that is Docker-native afaik.
On the Suse side, OBS should not require to setup a private instance and should
be available for open source projects.
One thing to consider too is that there are several distro
contributors on this list and some may be able to help setup some
distro- and arch-specific test beds.

Some frequent and important strace contributors also run several less
traveled architectures....
One thought could be to have a setup that makes it real easy for them
to setup continuous testing.


[1] https://github.com/strace/strace/blob/master/.travis.yml

-- 
Cordially
Philippe Ombredanne