Hi,

There isn't a way to pass the patch through to coverity through our scripting with how we have it written currently. It probably wouldn't be a big update to start running it based on a given patch provided, if you think there may be a somewhat regular need for this. I assume in this case we would not want to push the result to the coverity website, but rather just print out the result (to be shared on the mailing list or whatnot).

Otherwise, presumably it would be possible for us to manually spin up our coverity container image, apply the series, and run the coverity check.

I see you have merged this though. I will go ahead and trigger a coverity run now, just so that you get the results faster. Sorry about the wait here.

On Wed, Nov 6, 2024 at 3:24 PM David Marchand <david.marchand@redhat.com> wrote:
On Tue, Nov 5, 2024 at 10:05 PM David Marchand
<david.marchand@redhat.com> wrote:
> On Thu, Oct 24, 2024 at 5:20 PM Robin Jarry <rjarry@redhat.com> wrote:
> >
> > Here are fixes for three coverity issues:
>
> This series fixes two coverity issues. The fixes look correct.
> But the Coverity reports are not obvious to me.
>
> Is there a way to pass those fixes through Coverity to confirm the two
> issues are indeed fixed?

Well, let's get those fixes in.
We will have the answer tomorrow.

Series applied, thanks.


--
David Marchand