[Pdbg] [PATCH 1/2] Move build.sh to utils directory

Joel Stanley joel at jms.id.au
Mon Aug 13 18:17:46 AEST 2018


On Mon, 13 Aug 2018 at 17:22, Amitay Isaacs <amitay at ozlabs.org> wrote:
>
> On Mon, 2018-08-13 at 17:13 +0930, Joel Stanley wrote:
> > On Mon, 13 Aug 2018 at 16:51, Amitay Isaacs <amitay at ozlabs.org>
> > wrote:
> > >
> > > On Mon, 2018-08-13 at 16:06 +0930, Joel Stanley wrote:
> > > > Update travis config to point to the new location.
> > > >
> > > > Add a symlink so other CI still works, we will remove this once
> > > > it
> > > > has
> > > > been moved over.
> > > >
> > > > Signed-off-by: Joel Stanley <joel at jms.id.au>
> > >
> > > Can we also add "make check" to build.sh?
> > >
> > > For build.sh, can we just assume it's going to be run on x86_64
> > > platform?  That should avoid the need for --host=x86_64-linux-gnu.
> > > Also, simplifies adding "make check" to build.sh (we don't have to
> > > worry about where to run "make check").
> >
> > We were doing builds on ppc64le hosts. Since adding the arm cross
> > compile I had to disable it, as Ubuntu ppc64le doesn't build the ARM
> > cross compiler. I'd like to get this going again.
> >
> > Make check as it's written only uses the host compiler, so it will
> > work on ppc64le today.
> >
> > The reason we have broken out make check into a different script is
> > so
> > it shows up as a separate check in patchwork's 'checks' section. We
> > will run the build script first, and the check second, so any build
> > errors are not confused with failing tests.
>
> Ah.  I thought build.sh was for Jenkins/Patchwork and travis.yml was
> for CI.
>
> Does that mean we run CI on pdbg-master (not just patches)?  And where
> does it run?

Currently we have Travis enabled, which means whenever a branch is
pushed to Github (and the user has Travis enabled), it will run
against that branch. This can be useful for testing before submission:

https://travis-ci.org/shenki/pdbg/builds/415311411

I got Stewart to turn this on for the main repository too, so builds
should start showing up here:

 https://travis-ci.org/open-power/pdbg

We also have snowpatch building patches that are sent to the mailing
list, and updating the "tested" status on patchwork. I think will also
email you if your patch is broken:

 https://patchwork.ozlabs.org/patch/956833/

There's a different job that will build master. This one doesn't
report anywhere yet:

 https://openpower.xyz/job/openpower/job/pdbg-master/

I will add some documentation to the repository explaining all of
this. The missing piece is to run this on real hardware somewhere.

Cheers,

Joel


More information about the Pdbg mailing list