Re: [PATCH] scripts/coverity-scan/COMPONENTS.md: Update paths to match gitlab CI

2024-06-04 Thread Philippe Mathieu-Daudé
On 4/6/24 15:32, Peter Maydell wrote: On Fri, 31 May 2024 at 16:17, Philippe Mathieu-Daudé wrote: Hi Peter, On 31/5/24 16:21, Peter Maydell wrote: If there are any other changes we want to make to our component regexes, now would be a great time to suggest them, because this change is goin

Re: [PATCH] scripts/coverity-scan/COMPONENTS.md: Update paths to match gitlab CI

2024-06-04 Thread Peter Maydell
On Fri, 31 May 2024 at 16:17, Philippe Mathieu-Daudé wrote: > > Hi Peter, > > On 31/5/24 16:21, Peter Maydell wrote: > > If there are any other changes we want to make to our component > > regexes, now would be a great time to suggest them, because this > > change is going to involve "delete ever

Re: [PATCH] scripts/coverity-scan/COMPONENTS.md: Update paths to match gitlab CI

2024-05-31 Thread Philippe Mathieu-Daudé
Hi Peter, On 31/5/24 16:21, Peter Maydell wrote: Since commit 83aa1baa069c we have been running the build for Coverity Scan as a Gitlab CI job, rather than the old setup where it was run on a local developer's machine. This is working well, but the absolute paths of files are different for the

[PATCH] scripts/coverity-scan/COMPONENTS.md: Update paths to match gitlab CI

2024-05-31 Thread Peter Maydell
Since commit 83aa1baa069c we have been running the build for Coverity Scan as a Gitlab CI job, rather than the old setup where it was run on a local developer's machine. This is working well, but the absolute paths of files are different for the Gitlab CI job, which means that the regexes we use t