[CRIU] [PATCH] jenkins: build a coverage report if GCOV is set
Andrew Vagin
avagin at virtuozzo.com
Thu Mar 24 12:04:51 PDT 2016
On Thu, Mar 24, 2016 at 09:18:14PM +0300, Pavel Emelyanov wrote:
> On 03/24/2016 07:26 PM, Andrey Vagin wrote:
> > From: Andrew Vagin <avagin at virtuozzo.com>
>
> Some explanation would be nice.
> Isn't it built now? How has it happened? I thought Sergey made these ... jenkinsjobs?
> No?
With this patch we can do parameterized jobs, so we will not need to
generate separate set of jobs to make a coverage report.
>
> > Signed-off-by: Andrew Vagin <avagin at virtuozzo.com>
> > ---
> > test/jenkins/criu-lib.sh | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/test/jenkins/criu-lib.sh b/test/jenkins/criu-lib.sh
> > index 14ae9f3..60777dd 100644
> > --- a/test/jenkins/criu-lib.sh
> > +++ b/test/jenkins/criu-lib.sh
> > @@ -1,3 +1,9 @@
> > +function exit_hook()
> > +{
> > + test -z "$GCOV" && return
> > + make gcov
> > +}
> > +
> > function prep()
> > {
> > # systemd executes jenkins in a separate sched cgroup.
> > @@ -11,7 +17,7 @@ function prep()
> > make -j 4 -C test/zdtm/ &&
> > make -C test zdtm_ct &&
> > mkdir -p test/report &&
> > - true
> > + trap exit_hook EXIT
> > }
> >
> > function mount_tmpfs_to_dump()
> >
>
More information about the CRIU
mailing list