[cfe-dev] scan-build output on the front page (llvm.org)
Sylvestre Ledru via cfe-dev
cfe-dev at lists.llvm.org
Sat Jul 7 04:05:52 PDT 2018
The reports are generated by the same platform which generates apt.llvm.org.
They have been failing because, the build fails with:
make: /bin/sh: Command not found
I haven't found the reason why
Full log: https://llvm-jenkins.debian.net/job/llvm-toolchain-scan-build-binaries/architecture=amd64,distribution=unstable,label=master/597/console
It seems to be scan-build specific as I don't experience such issues with the regular builds.
Help or suggestions are be welcome :)
FYI, the scan-build configuration is done here:
Le 20/06/2018 à 08:49, Vlad Tsyrklevich a écrit :
> Last relevant change I see
> is https://llvm.org/viewvc/llvm-project?view=revision&revision=213129 from
> 4 years ago. The coverage report is still updated, adding Sylvestre in
> case he knows the source of the reports.
> On Mon, Jun 18, 2018 at 10:21 AM Anna Zaks <ganna at apple.com
> <mailto:ganna at apple.com>> wrote:
> + Artem and Devin
> I do not recall who posts those scans. Maybe looking at the commit
> history for llvm.org <http://llvm.org> could give us a clue?
> Would be also good to find out if the latest analyzer from master
> is used for the scans or if they are based on the scan-build we
>> On Jun 16, 2018, at 10:36 PM, Vlad Tsyrklevich
>> <vlad at tsyrklevich.net <mailto:vlad at tsyrklevich.net>> wrote:
>> Is the scan-build output
>> <https://llvm.org/reports/scan-build> linked from the sidebar of
>> the front page meant to be updated automatically? Looking at the
>> results it seemed like there were a good amount of true positive
>> hits but the last run looks like it was in April. That's long
>> enough that the results are not very useful for identifying bugs
>> in code you own, or for that matter filing bugs against FPs in
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev