mirrors/llvm-project
0
0
Fork 0
mirror of https://github.com/llvm/llvm-project.git synced 2025-04-28 09:46:06 +00:00
Code Issues Projects Releases Wiki Activity
llvm-project/compiler-rt/test/fuzzer/fork.test

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

22 lines
1.2 KiB
Plaintext
Raw Normal View History

[fuzzer] Convert tests to check 'target=...' Part of the project to eliminate special handling for triples in lit expressions.
2022-12-16 11:41:28 -08:00
# UNSUPPORTED: darwin, target={{.*freebsd.*}}, target=aarch64{{.*}}
[libFuzzer] teach the fork mode to ignore OOMs and timeouts llvm-svn: 353792
2019-02-12 02:18:53 +00:00
BINGO: BINGO
[libFuzzer] run the -fork=1 tests only on linux llvm-svn: 353777
2019-02-12 00:29:51 +00:00
RUN: %cpp_compiler %S/SimpleTest.cpp -o %t-SimpleTest
[libFuzzer] Increase timeouts on fork tests and skip one on aarch64 The tests fork.text, fork.sigusr.test and fork-ubsan.test intermittently fail on the aarch64 buildbots. Input gathered from the fork.sigusr.test implies that when the builder is under load the timeout value is not sufficient. The fork-ubsan.test doesn't have a timeout and I think is not always finding the error after 10000 runs so I've marked it as unsupported for now. Differential Revision: https://reviews.llvm.org/D61449 llvm-svn: 360126
2019-05-07 09:31:14 +00:00
RUN: not %run %t-SimpleTest -fork=1 2>&1 | FileCheck %s --check-prefix=BINGO
[libFuzzer] run the -fork=1 tests only on linux llvm-svn: 353777
2019-02-12 00:29:51 +00:00
[libFuzzer] teach the fork mode to ignore OOMs and timeouts llvm-svn: 353792
2019-02-12 02:18:53 +00:00
TIMEOUT: ERROR: libFuzzer: timeout
RUN: %cpp_compiler %S/TimeoutTest.cpp -o %t-TimeoutTest
[libFuzzer] Increase timeouts on fork tests and skip one on aarch64 The tests fork.text, fork.sigusr.test and fork-ubsan.test intermittently fail on the aarch64 buildbots. Input gathered from the fork.sigusr.test implies that when the builder is under load the timeout value is not sufficient. The fork-ubsan.test doesn't have a timeout and I think is not always finding the error after 10000 runs so I've marked it as unsupported for now. Differential Revision: https://reviews.llvm.org/D61449 llvm-svn: 360126
2019-05-07 09:31:14 +00:00
RUN: not %run %t-TimeoutTest -fork=1 -timeout=1 -ignore_timeouts=0 2>&1 | FileCheck %s --check-prefix=TIMEOUT
[libFuzzer] teach the fork mode to ignore OOMs and timeouts llvm-svn: 353792
2019-02-12 02:18:53 +00:00
OOM: ERROR: libFuzzer: out-of-memory
RUN: %cpp_compiler %S/OutOfMemoryTest.cpp -o %t-OutOfMemoryTest
[libFuzzer] Increase timeouts on fork tests and skip one on aarch64 The tests fork.text, fork.sigusr.test and fork-ubsan.test intermittently fail on the aarch64 buildbots. Input gathered from the fork.sigusr.test implies that when the builder is under load the timeout value is not sufficient. The fork-ubsan.test doesn't have a timeout and I think is not always finding the error after 10000 runs so I've marked it as unsupported for now. Differential Revision: https://reviews.llvm.org/D61449 llvm-svn: 360126
2019-05-07 09:31:14 +00:00
RUN: not %run %t-OutOfMemoryTest -fork=1 -ignore_ooms=0 -rss_limit_mb=128 2>&1 | FileCheck %s --check-prefix=OOM
[libFuzzer] teach the fork mode to ignore OOMs and timeouts llvm-svn: 353792
2019-02-12 02:18:53 +00:00
fix comment llvm-svn: 359586
2019-04-30 17:58:57 +00:00
# access-violation is the error thrown on Windows. Address will be smaller on i386.
Revert "Revert "Temporarily do not drop volatile stores before unreachable"" This reverts commit 52aeacfbf5ce5f949efe0eae029e56db171ea1f7. There isn't full agreement on a path forward yet, but there is agreement that this shouldn't land as-is. See discussion on https://reviews.llvm.org/D105338 Also reverts unreviewed "[clang] Improve `-Wnull-dereference` diag to be more in-line with reality" This reverts commit f4877c78c0fc98be47b926439bbfe33d5e1d1b6d. And all the related changes to tests: This reverts commit 9a0152799f8e4a59e0483728c9f11c8a7805616f. This reverts commit 3f7c9cc27422f7302cf5a683eeb3978e6cb84270. This reverts commit 329f8197ef59f9bd23328b52d623ba768b51dbb2. This reverts commit aa9f58cc2c48ca6cfc853a2467cd775dc7622746. This reverts commit 2df37d5ddd38091aafbb7d338660e58836f4ac80. This reverts commit a72a44181264fd83e05be958c2712cbd4560aba7.
2021-07-09 11:39:40 -04:00
CRASH: {{SEGV|access-violation}} on unknown address 0x00000000
[libFuzzer] teach the fork mode to ignore OOMs and timeouts llvm-svn: 353792
2019-02-12 02:18:53 +00:00
RUN: %cpp_compiler %S/ShallowOOMDeepCrash.cpp -o %t-ShallowOOMDeepCrash
[libFuzzer] Increase timeouts on fork tests and skip one on aarch64 The tests fork.text, fork.sigusr.test and fork-ubsan.test intermittently fail on the aarch64 buildbots. Input gathered from the fork.sigusr.test implies that when the builder is under load the timeout value is not sufficient. The fork-ubsan.test doesn't have a timeout and I think is not always finding the error after 10000 runs so I've marked it as unsupported for now. Differential Revision: https://reviews.llvm.org/D61449 llvm-svn: 360126
2019-05-07 09:31:14 +00:00
RUN: not %run %t-ShallowOOMDeepCrash -fork=1 -rss_limit_mb=128 2>&1 | FileCheck %s --check-prefix=CRASH
[libFuzzer] form mode: add -ignore_crashes flag, honor the max_total_time flag, print the number of ooms/timeouts/crashes, fix a typo llvm-svn: 354175
2019-02-15 21:51:15 +00:00
MAX_TOTAL_TIME: INFO: fuzzed for {{.*}} seconds, wrapping up soon
MAX_TOTAL_TIME: INFO: exiting: {{.*}} time:
Change filecheck default to dump input on failure Having the input dumped on failure seems like a better default: I debugged FileCheck tests for a while without knowing about this option, which really helps to understand failures. Remove `-dump-input-on-failure` and the environment variable FILECHECK_DUMP_INPUT_ON_FAILURE which are now obsolete. Differential Revision: https://reviews.llvm.org/D81422
2020-03-27 23:58:06 +00:00
RUN: not %run %t-ShallowOOMDeepCrash -fork=1 -rss_limit_mb=128 -ignore_crashes=1 -max_total_time=10 2>&1 | FileCheck %s --check-prefix=MAX_TOTAL_TIME
Reference in New Issue Copy Permalink