1672410 - [Automated review] Errors reported, but they aren't reported by static-analysis

Status: RESOLVED DUPLICATE of bug 1671224

(Developer Infrastructure :: Source Code Analysis, defect, P3)

Description

[Mike Kaply [:mkaply]]

Phabricator URL: https://phabricator.services.mozilla.com/D93390

I got this error:

Code analysis found 2 defects in the diff 355692:

2 defects found by clang-tidy

You can run this analysis locally with:

./mach static-analysis check --outgoing (C/C++)

But when I run that command locally, I get:

$ ./mach static-analysis check --outgoing
 0:03.65 checking for vcs source checkout...
 0:03.65 hg
 0:03.90 Adding configure options from d:\mozilla-unified\mozconfig
 0:03.90 checking for host system type...
 0:03.90 x86_64-pc-mingw32
 0:03.90 checking for target system type...
 0:03.91 x86_64-pc-mingw32
 0:04.36 c:\mozilla-build\bin\mozmake.EXE -C d:/mozilla-unified/obj-x86_64-pc-mingw32 -j8 -s -w pre-export
 0:04.52 mozmake.EXE: Entering directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:04.55 BUILDSTATUS TIERS pre-export
 0:04.57 BUILDSTATUS TIER_START pre-export
 0:04.67 mozmake.EXE[1]: Entering directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:04.97 Elapsed: 0.00s; From dist/private: Kept 0 existing; Added/updated 0; Removed 0 files and 0 directories.
 0:04.98 Elapsed: 0.00s; From dist/public: Kept 0 existing; Added/updated 0; Removed 0 files and 0 directories.
 0:05.02 Elapsed: 0.03s; From dist/xpi-stage: Kept 90 existing; Added/updated 0; Removed 0 files and 0 directories.
 0:05.76 Elapsed: 0.80s; From _tests: Kept 0 existing; Added/updated 1363; Removed 0 files and 0 directories.
 0:05.88 Elapsed: 0.91s; From dist/bin: Kept 0 existing; Added/updated 2569; Removed 0 files and 0 directories.
 0:06.89 Elapsed: 1.92s; From dist/include: Kept 0 existing; Added/updated 6484; Removed 0 files and 0 directories.
 0:06.91 mozmake.EXE[1]: Leaving directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:06.93 BUILDSTATUS TIER_FINISH pre-export
 0:06.93 mozmake.EXE: Leaving directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:07.01 c:\mozilla-build\bin\mozmake.EXE -C d:/mozilla-unified/obj-x86_64-pc-mingw32 -j8 -s -w export
 0:07.12 mozmake.EXE: Entering directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:07.12 ./buildid.h.stub
 0:07.12 ./source-repo.h.stub
 0:08.26 BUILDSTATUS TIERS export
 0:08.28 BUILDSTATUS TIER_START export
 0:08.39 mozmake.EXE[1]: Entering directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:08.39 ./application.ini.stub
 0:08.79 mozmake.EXE[2]: Entering directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32/xpcom/xpidl'
 0:08.80 mozmake.EXE[2]: Entering directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32/browser/locales'
 0:08.85 mozmake.EXE[2]: Leaving directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32/browser/locales'
 0:08.95 ./application.ini.h.stub
 0:09.07 mozmake.EXE[2]: Leaving directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32/xpcom/xpidl'
 0:09.28 mozmake.EXE[1]: Leaving directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:09.30 BUILDSTATUS TIER_FINISH export
 0:09.30 mozmake.EXE: Leaving directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:09.39 c:\mozilla-build\bin\mozmake.EXE -C d:/mozilla-unified/obj-x86_64-pc-mingw32 -j8 -s -w pre-compile
 0:09.49 mozmake.EXE: Entering directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:09.51 BUILDSTATUS TIERS pre-compile
 0:09.53 BUILDSTATUS TIER_START pre-compile
 0:09.63 mozmake.EXE[1]: Entering directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:10.00 mozmake.EXE[1]: Leaving directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:10.01 BUILDSTATUS TIER_FINISH pre-compile
 0:10.02 mozmake.EXE: Leaving directory 'd:/mozilla-unified/obj-x86_64-pc-mingw32'
 0:13.65 There are no files eligible for analysis. Please note that 'header' files cannot be used for analysis since they do not consist compilation units.
 0:13.65 There are no files eligible for analysis. Please note that 'header' files cannot be used for analysis since they do not consist compilation units.

Comment 1

[Andi [:andi]]

Was also this happening if you were running static-analysis on the specific files?

Comment 3

[Mike Kaply [:mkaply]]

Was also this happening if you were running static-analysis on the specific files?

Unfortunately I didn't check and can't easily now.