Re: [Xen-devel] [PATCH] automation: introduce a script for build test

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, Jul 24, 2018 at 01:01:52PM -0500, Doug Goldstein wrote:
> On Tue, Jul 24, 2018 at 05:56:51PM +0100, Wei Liu wrote:
> > Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
> > Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx>
> > ---
> > This is a script I wrote previously for build test.
> 
> Goal here is to bisect a series to find the build failure? We could

No, not to bisect.  git-bisect would be good enough for bisection and I
don't intent to poorly reinvent my own wheel.

We have seen many cases the build would be broken in the middle of a
long series, but the series as a whole still builds.  This script is to
keep every commit in a series buildable so it doesn't break bisection.

And despite asking contributors nicely to do so, they don't tend to have
the time to write all the commands in a safe way.

> > diff --git a/automation/scripts/build-test.sh 
> > b/automation/scripts/build-test.sh
> > new file mode 100755
> > index 0000000000..885e5f7a13
> > --- /dev/null
> > +++ b/automation/scripts/build-test.sh
> > @@ -0,0 +1,68 @@
> > +#!/bin/bash
> > +
> > +# Run command on every commit within the range specified. If no command is
> > +# provided, use the default one to clean and build the whole tree.
> > +#
> > +# The default rune is rather simple. To do a cross-build, please put your 
> > usual
> > +# build rune in a shell script and invoke it with this script.
> > +
> > +if ! test -f xen/common/kernel.c; then
> > +    echo "Please run this script from top-level directory"
> > +    exit 1
> > +fi
> 
> You could make it run from anywhere if you did:
> pushd `git rev-parse --show-toplevel`

Ah, thanks for the tip.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel