All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
	ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 2/3] Add a weekly coverity flight
Date: Wed, 3 Feb 2016 10:46:27 +0000	[thread overview]
Message-ID: <56B1DA83.20306@citrix.com> (raw)
In-Reply-To: <1454494797.25207.39.camel@citrix.com>

On 03/02/16 10:19, Ian Campbell wrote:
> On Wed, 2016-02-03 at 09:46 +0000, Ian Campbell wrote:
>>  [...]
>> +sub build () {
>> +    my $make = "make $makeflags";
>> +
>> +    # Pre build things we don't want coverity to scan, but which are
>> +    # normally built by some other command.
>> +    target_cmd_build($ho, 1000, $builddir, <<END);
>> +cd $builddir/xen
>> +./configure
>> +$make -C tools/firmware/etherboot all
>> +$make mini-os-dir
>> +END
>> +
>> +    # Now the stuff we want coverity to look at
>> +    target_cmd_build($ho, 9000, $builddir, <<END);
>> +cd $builddir/xen
>> +export PATH=$builddir/covtools/bin:\$PATH
>> +cov-build --dir cov-int $make -C extras/mini-os/
>> +cov-build --dir cov-int $make xen tools
> This omits building stubdom, which Andy's original script also did.
>
> However stubdom exists as a category in the scan webui and there have
> previously been results for stubdoms.
>
> Andy, I presume you deliberately started excluding stubdoms at some point?
> I think this is probably the right thing to do, at least for now, since
> stubdoms run with guest privileges so aren't hugely interesting, plus they
> include an awful lot of third party code which we don't want to be
> scanning+triaging (especially given how out of date some of the code is).

Correct.  That is precisely why I prevented stubdom and etherboot from
being scanned.

~Andrew

  reply	other threads:[~2016-02-03 10:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03  9:46 [PATCH 1/3] Move collectversions from ts-xen-build into Osstest::BuildSupport Ian Campbell
2016-02-03  9:46 ` [PATCH 2/3] Add a weekly coverity flight Ian Campbell
2016-02-03  9:46   ` [PATCH 3/3] make-coverity-flight: set coverity_upload=true Ian Campbell
2016-02-03 12:13     ` Ian Jackson
2016-02-03 10:19   ` [PATCH 2/3] Add a weekly coverity flight Ian Campbell
2016-02-03 10:46     ` Andrew Cooper [this message]
2016-02-03 12:13       ` Ian Jackson
2016-02-03 12:12   ` Ian Jackson
2016-02-03 12:46     ` Ian Campbell
2016-02-03  9:59 ` [PATCH 1/3] Move collectversions from ts-xen-build into Osstest::BuildSupport Ian Campbell
2016-02-03 12:02 ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56B1DA83.20306@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.