scan-build output on the front page (llvm.org)

Is the scan-build output 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 checkers.

  • Artem and Devin

I do not recall who posts those scans. Maybe looking at the commit history for 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 publish/“release”.

Anna

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.

Hello,

The reports are generated by the same platform which generates apt.llvm.org.

They have been failing because, the build fails with:

make[4]: /bin/sh: Command not found
I haven't found the reason why 
Full log: 
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:

Cheers,
Sylvestre

Hello,

The reports are generated by the same platform which generates apt.llvm.org.

They have been failing because, the build fails with:

make[4]: /bin/sh: Command not found

It seems the issue is that the bot is using Make instead of Ninja for building,
and clangd Make has a hardcoded path to shell (which is probably in /usr/bin on the bot in question).
Sylvestre, could you reconfigure the bot to use Ninja?

George

Hello,

Cool! Most likely /bin/sh was changed to "/usr/bin/env sh”