FreeBSD CI Weekly Report 2018-01-20

[Stefan Esser]

Am 22.01.19 um 05:44 schrieb Li-Wen Hsu:
> (bcc -current and -stable for more audience)
> 
> FreeBSD CI Weekly Report 2018-01-20
> ===================================
> 
> Here's a summary of the FreeBSD Continuous Integration results for the
> period from 2018-01-14 to 2018-01-20 (and some older results because
> this is the first report).
> 
> During this period, we have 1961 builds (89.8% pass, 8.7% failed, 1.5%
> exception) were executed on aarch64, amd64, armv6, armv7, i386, mips,
> mips64, powerpc, powerpc64, powerpcspe, riscv64, sparc64 architectures;
> and 496 test runs (51% pass, 49% unstable) were executed on amd64, i386,
> riscv64 architectures.

Thank you for sending this report, very appreciated!

> If any of the issues found by CI are in your area of interest or
> expertise please investigate the PRs listed below.
> 
> Web version and archive are available at
> http://hackfoldr.org/freebsd-ci-report/
> Any help and suggestion are welcome.

Well, too bad, that this site displays only a grey background in my
Firefox with uMatrix and uBlock origin, even though I have allowed
embedding Javascript from apis.google.com and content.googleapis.com
and frames from the latter. (But even deactivating uMatrix/uBlock for
this site did not show any significant content.)

> * Result of daily Clang scan build:
>   https://ci.freebsd.org/job/FreeBSD-head-scan_build/lastCompletedBuild/clangScanBuildBugs/

I have looked at a few of the findings and committed a simple change
to silence a false positive (actually safe use of strcpy() in kbdmap.c).

Is there a way to tag such false positives in a way that they are not
reported over and over by the Clang Scan build?

Another report lead to the change uploaded to Arcanist as D18921:

	https://reviews.freebsd.org/D18921

The patch causes line breaks and at least the strcpy uses reported by
the scan are actually uncritical (since the strings are small), there
was an actual potential buffer overflow near by (and I'd rather fix both
and silence the scan report that way).

Anyway, a very useful report and a real help to get issues fixed!

Best regards, STefan