summaryrefslogtreecommitdiffstats
path: root/clang/tools/scan-build-py/tests/unit/test_report.py
Commit message (Collapse)AuthorAgeFilesLines
* Update the file headers across all of the LLVM projects in the monorepoChandler Carruth2019-01-191-4/+3
| | | | | | | | | | | | | | | | | to reflect the new license. We understand that people may be surprised that we're moving the header entirely to discuss the new license. We checked this carefully with the Foundation's lawyer and we believe this is the correct approach. Essentially, all code in the project is now made available by the LLVM project under our new license, so you will see that the license headers include that license only. Some of our contributors have contributed code under our old license, and accordingly, we have retained a copy of our old license notice in the top-level files in each project and repository. llvm-svn: 351636
* [scan-build-py] merge runner module to analyzerLaszlo Nagy2017-04-071-1/+1
| | | | | | Differential Revision: https://reviews.llvm.org/D31237 llvm-svn: 299759
* [scan-build-py] move function report_directory from report module to analyze ↵Laszlo Nagy2017-02-141-13/+0
| | | | | | | | module Differential Revision: https://reviews.llvm.org/D29255 llvm-svn: 295045
* [scan-build-py] Increase precision of timestamp in report directory nameDevin Coughlin2016-09-061-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | This commit improves compatibility with the perl version of scan-build. The perl version of scan-build produces output report directories with increasing lexicographic ordering. This ordering is relied on by the CmpRuns.py tool in utils/analyzer when comparing results for build commands with multiple steps. That tool tries to line up the output directory for each step between different runs of the analyzer based on the increasing directory name. The python version of scan-build uses file.mkdtemp() with a time stamp prefix to create report directories. The timestamp has a 1-second precision. This means that when analysis of a single build step takes less than a second the ordering property that CmpRuns.py expects will sometimes not hold, depending on the timing and the random suffix generated by mkdtemp(). Ultimately this causes CmpRuns to incorrectly correlate results from build steps and report spurious differences between runs. This commit increases the precision of the timestamp used in scan-build-py to the microsecond level. This approach still has the same underlying issue -- but in practice analysis of any build step is unlikely to take less than a millisecond. Differential Revision: https://reviews.llvm.org/D24163 llvm-svn: 280768
* D17487: [analyzer][scan-build-py] flag filter modification for compilation ↵Laszlo Nagy2016-04-191-14/+16
| | | | | | database creation llvm-svn: 266726
* D9600: Add scan-build python implementationLaszlo Nagy2016-01-121-0/+146
llvm-svn: 257533
OpenPOWER on IntegriCloud