Searched refs:positives (Results 1 – 25 of 131) sorted by relevance
123456
/external/python/cpython2/Misc/ |
D | README.klocwork | 14 were false positives. However, there were numerous real issues 23 False positives were also annotated so that the comments can 27 some false positives and perform some additional checks. ~150 new
|
D | README.coverity | 13 were false positives. Over 70 issues were uncovered. 19 False positives were annotated so that the comments can
|
/external/python/cpython3/Misc/ |
D | README.coverity | 13 were false positives. Over 70 issues were uncovered. 19 False positives were annotated so that the comments can
|
/external/compiler-rt/test/tsan/Darwin/ |
D | ignored-interceptors.mm | 2 // system libraries on OS X. There are currently false positives coming from 8 // Check that without the flag, there are false positives.
|
/external/deqp/doc/testspecs/GLES31/ |
D | functional.sample_shading.txt | 61 positives. False positive may occur if distinct pixels with identical filter 64 and thus do not produce false positives.
|
/external/grpc-grpc/third_party/nanopb/tests/splint/ |
D | splint.rc | 32 # These tests give false positives, compiler typically has
|
/external/nanopb-c/tests/splint/ |
D | splint.rc | 32 # These tests give false positives, compiler typically has
|
/external/zlib/src/doc/ |
D | txtvsbin.txt | 25 the false positives that may occur when binary files containing large 90 positives). This, however, incurs a reduced precision overall, since 91 false positives are more likely to appear in binary files that contain
|
/external/curl/tests/data/ |
D | DISABLED | 19 # Pipelining test that is causing false positives a little too often
|
/external/libyuv/files/tools/msan/ |
D | blacklist.txt | 22 # False positives due to use of linux_syscall_support. http://crbug.com/394028
|
/external/toolchain-utils/android_bench_suite/ |
D | Hwui_flags_aosp.diff | 11 // GCC false-positives on this warning, and since we -Werror that's
|
D | Hwui_flags_internal.diff | 11 // GCC false-positives on this warning, and since we -Werror that's
|
/external/llvm/utils/valgrind/ |
D | i386-pc-linux-gnu.supp | 9 # Python false positives according to
|
D | x86_64-pc-linux-gnu.supp | 8 # Python false positives according to
|
/external/swiftshader/third_party/LLVM/utils/valgrind/ |
D | i386-pc-linux-gnu.supp | 9 # Python false positives according to
|
D | x86_64-pc-linux-gnu.supp | 8 # Python false positives according to
|
/external/swiftshader/third_party/llvm-7.0/llvm/utils/valgrind/ |
D | i386-pc-linux-gnu.supp | 9 # Python false positives according to
|
D | x86_64-pc-linux-gnu.supp | 8 # Python false positives according to
|
/external/skqp/site/dev/testing/ |
D | skiagold.md | 98 * Follow one of two options for handling former positives: 99 + Leave former positives as-is and let them fall off with time if there is 101 + Mark former positives as negative if needed to verify the change moving
|
/external/skia/site/dev/testing/ |
D | skiagold.md | 98 * Follow one of two options for handling former positives: 99 + Leave former positives as-is and let them fall off with time if there is 101 + Mark former positives as negative if needed to verify the change moving
|
/external/clang/docs/ |
D | ThreadSanitizer.rst | 92 instruments such functions to avoid false positives and provide meaningful stack 103 all. This can lead to false positives due to missed synchronization via atomic
|
/external/u-boot/scripts/coccinelle/misc/ |
D | badty.cocci | 6 //# to the the memory being allocated. There are false positives in cases the
|
/external/u-boot/scripts/coccinelle/iterators/ |
D | itnull.cocci | 3 //# False positives arise for some iterators that do not have this property,
|
/external/libyuv/files/tools/ubsan/ |
D | blacklist.txt | 10 # V8 gives too many false positives. Ignore them for now.
|
/external/deqp/doc/testspecs/GLES3/ |
D | functional.occlusion_query.txt | 48 allows false positives, i.e. the occlusion query can return true even if
|
123456