On Tue, 2017-03-07 at 10:02 +0100, Peter Meerwald-Stadler wrote:
> > Ack, go ahead and push this. Do we need to modify our Coverity
> > project
> > settings?
>
> pushed, no need to modify server side Coverity settings
>
> Philip can re-enable the periodic scans
Re-enabled, and I’ve queued a new
odel file must be uploaded by an admin to:
> https://scan.coverity.com/projects/pulseaudio?tab=analysis_settings
>
> the pa_assert_se() macro needs to be rewritten for Coverity so that
> the assignment is not declared a side-effect
>
> Signed-off-by: Peter Meerwald-Stadler
>
y impact on the others.
This is a problem which needs to be fixed in upstream PulseAudio. It
doesn’t just stop jenkins.fdo from submitting sane Coverity results —
it’s configuration which has to be repeated by every PA maintainer who
wants to submit results.
Philip
> > On Wed, 2017-02-22
re-enable the builds in
Jenkins when someone does fix this though. Arun seemed to approve of
them, at least.
On Wed, 2017-02-22 at 12:06 +, Philip Withnall wrote:
> Hi,
>
> On Wed, 2017-02-22 at 11:52 +0000, Philip Withnall wrote:
> > Apologies if this has been discussed
Hi,
On Wed, 2017-02-22 at 12:38 +0100, Peter Meerwald-Stadler wrote:
> as written and discussed before (
> https://lists.freedesktop.org/archives/pulseaudio-discuss/2015-Septem
> ber/024378.html
> http://comments.gmane.org/gmane.comp.audio.pulseaudio.general/19270
> http://pulseaudio-discuss.freed
Hi,
On Wed, 2017-02-22 at 11:52 +, Philip Withnall wrote:
> Apologies if this has been discussed before (I don’t follow
> PulseAudio
> development), but why not stick this in the server-side Coverity
> modelling file? Does that not work?
Having just tried it, apparently it doe
