Home
last modified time | relevance | path

Searched +full:fuzz +full:- +full:seconds (Results 1 – 25 of 105) sorted by relevance

12345

/external/oss-fuzz/docs/getting-started/
Dcontinuous_integration.md1 ---
6 permalink: /getting-started/continuous-integration/
7 ---
11 OSS-Fuzz offers **CIFuzz**, a GitHub action/CI job that runs your fuzz targets
26 * The crash does not occur on older OSS-Fuzz builds. (If the crash does occur
30 If your project supports [OSS-Fuzz's code coverage]({{ site.baseurl }}/advanced-topics/code-coverag…
35 CIFuzz uses 30 day old/public regressions and corpora from OSS-Fuzz. This makes
40 1. Your project must be integrated with OSS-Fuzz.
42 1. Your repository needs to be cloned with `git` in oss-fuzz Dockerfile (do not use `go get` or oth…
49 1. Copy the example [`main.yml`](https://github.com/google/oss-fuzz/blob/master/infra/cifuzz/exampl…
[all …]
/external/oss-fuzz/infra/cifuzz/actions/run_fuzzers/
Daction.yml2 name: 'run-fuzzers'
3 description: 'Runs fuzz target binaries for a specified length of time.'
5 oss-fuzz-project-name:
6 description: 'The OSS-Fuzz project name.'
12 fuzz-seconds:
13 description: 'The total time allotted for fuzzing in seconds.'
16 dry-run:
22 run-fuzzers-mode:
26 "batch" is for non-interactive fuzzing of an entire project.
30 github-token:
[all …]
/external/AFLplusplus/test/
Dtest-qemu-mode.sh3 . ./test-pre.sh
6 test -z "$AFL_CC" && {
16 test -e ../afl-qemu-trace && {
17 cc -pie -fPIE -o test-instr ../test-instr.c
18 cc -o test-compcov test-compcov.c
19 test -e test-instr -a -e test-compcov && {
21 mkdir -p in
23 $ECHO "$GREY[*] running afl-fuzz for qemu_mode, this will take approx 10 seconds"
25 ../afl-fuzz -m ${MEM_LIMIT} -V10 -Q -i in -o out -- ./test-instr >>errors 2>&1
27 test -n "$( ls out/default/queue/id:000002* 2>/dev/null )" && {
[all …]
Dtest-unicorn-mode.sh3 . ./test-pre.sh
6 test -d ../unicorn_mode/unicornafl -a -e ../unicorn_mode/unicornafl/Makefile && {
7 …test -e ../unicorn_mode/samples/python_simple/simple_target.bin -a -e ../unicorn_mode/samples/comp…
13 PYTHONS="`command -v python3` `command -v python` `command -v python2`"
17 if $PYTHON -c "import setuptools" ; then
28 … echo "[-] Error: Python setup-tools not found. Run 'sudo apt-get install python-setuptools'."
36 … $ECHO "$GREY[*] running afl-fuzz for unicorn_mode (persistent), this will take approx 25 seconds"
37 …AFL_DEBUG_CHILD=1 ../../../afl-fuzz -m none -V25 -U -i sample_inputs -o out -d -- ./harness @@ >>e…
38 test -n "$( ls out/default/queue/id:000002* 2>/dev/null )" && {
39 $ECHO "$GREEN[+] afl-fuzz is working correctly with unicorn_mode (persistent)"
[all …]
Dtest-frida-mode.sh3 . ./test-pre.sh
6 test -z "$AFL_CC" && {
16 test -e ../afl-frida-trace.so && {
17 cc -no-pie -o test-instr ../test-instr.c
18 cc -o test-compcov test-compcov.c
19 test -e test-instr -a -e test-compcov && {
21 mkdir -p in
23 $ECHO "$GREY[*] running afl-fuzz for frida_mode, this will take approx 10 seconds"
25 …AFL_DEBUG=1 AFL_FRIDA_VERBOSE=1 ../afl-fuzz -m ${MEM_LIMIT} -V10 -O -i in -o out -- ./test-instr >…
27 test -n "$( ls out/default/queue/id:000002* 2>/dev/null )" && {
[all …]
Dtest-custom-mutators.sh3 . ./test-pre.sh
6 test "1" = "`../afl-fuzz | grep -i 'without python' >/dev/null; echo $?`" && {
9 …test -e test-custom-mutator.c -a -e ${CUSTOM_MUTATOR_PATH}/example.c -a -e ${CUSTOM_MUTATOR_PATH}/…
12 test -e ../afl-clang-fast && {
13 ../afl-clang-fast -o test-custom-mutator test-custom-mutator.c > /dev/null 2>&1
15 test -e ../afl-gcc-fast && {
16 ../afl-gcc-fast -o test-custom-mutator test-custom-mutator.c > /dev/null 2>&1
18 ../afl-gcc -o test-custom-mutator test-custom-mutator.c > /dev/null 2>&1
22 test -e ../afl-clang-fast && {
23 ../afl-clang-fast -o test-multiple-mutators test-multiple-mutators.c > /dev/null 2>&1
[all …]
Dtest-performance.sh7 test -z "$FILE" && FILE=.afl_performance
9 test -e $FILE || {
11 echo Press ENTER to continue or CONTROL-C to abort
15 test -e ./test-performance.sh || { echo Error: this script must be run from the directory in which …
37 test -e /usr/local/bin/opt && {
40 # on MacOS X we prefer afl-clang over afl-gcc, because
41 # afl-gcc does not work there
42 test `uname -s` = 'Darwin' -o `uname -s` = 'FreeBSD' && {
43 AFL_GCC=afl-clang
46 AFL_GCC=afl-gcc
[all …]
/external/oss-fuzz/infra/cifuzz/external-actions/run_fuzzers/
Daction.yml2 name: 'run-fuzzers'
3 description: 'Runs fuzz target binaries for a specified length of time.'
9 fuzz-seconds:
10 description: 'The total time allotted for fuzzing in seconds.'
13 dry-run:
19 run-fuzzers-mode:
23 "batch" is for non-interactive fuzzing of an entire project.
27 github-token:
32 TODO(https://github.com/google/oss-fuzz/pull/5841#discussion_r639393361):
35 storage-repo:
[all …]
/external/python/cpython2/Lib/test/
Dtest_timeout.py61 self.assertRaises(ValueError, self.sock.settimeout, -1)
62 self.assertRaises(ValueError, self.sock.settimeout, -1L)
63 self.assertRaises(ValueError, self.sock.settimeout, -1.0)
96 # When fuzz was at 1.0, I (tim) routinely saw bogus failures on Win2K
99 fuzz = 2.0 variable in TimeoutTestCase
125 _delta = abs(_t1 - _t2)
126 self.assertTrue(_delta < _timeout + self.fuzz,
127 "timeout (%g) is more than %g seconds more than expected (%g)"
128 %(_delta, self.fuzz, _timeout))
142 _delta = abs(_t1 - _t2)
[all …]
/external/oss-fuzz/infra/cifuzz/
Dfuzz_target.py7 # http://www.apache.org/licenses/LICENSE-2.0
14 """A module to handle running a fuzz target for a specified amount of time."""
22 import clusterfuzz.fuzz
27 format='%(asctime)s - %(name)s - %(levelname)s - %(message)s',
32 LIBFUZZER_OPTIONS = ['-seed=1337', '-len_control=0']
39 # Seconds on top of duration until a timeout error is raised.
66 class FuzzTarget: # pylint: disable=too-many-instance-attributes
67 """A class to manage a single fuzz target.
70 target_name: The name of the fuzz target.
71 duration: The length of time in seconds that the target should run.
[all …]
Dexample_main.yml5 runs-on: ubuntu-latest
7 - name: Build Fuzzers
9 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
11 oss-fuzz-project-name: 'example'
12 dry-run: false
13 - name: Run Fuzzers
14 uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
16 oss-fuzz-project-name: 'example'
17 fuzz-seconds: 600
18 dry-run: false
[all …]
/external/rust/crates/libz-sys/src/zlib-ng/.github/workflows/
Dfuzz.yml1 name: CI Fuzz
6 - stable
7 - develop
8 - pre-release
9 - '2.*'
11 - '*'
15 runs-on: ubuntu-latest
17 - name: Build Fuzzers
18 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
20 oss-fuzz-project-name: 'zlib-ng'
[all …]
/external/flatbuffers/.github/workflows/
Dmain.yml1 name: OSS-Fuzz
2 permissions: read-all
7 - master
9 - include/**
10 - src/**
11 - tests/**.cpp
12 - tests/**.h
15 runs-on: ubuntu-latest
17 - name: Build Fuzzers
19 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
[all …]
/external/oss-fuzz/docs/clusterfuzzlite/
Drunning_clusterfuzzlite.md1 ---
7 permalink: /clusterfuzzlite/running-clusterfuzzlite/
8 ---
12 - TOC
14 ---
38 This use-case is important because it allows ClusterFuzzLite to find bugs before
40 To use Code Review Fuzzing, set the configuration option `clusterfuzzlite-task`
41 to `code-review`.
42 If you are familiar with OSS-Fuzz's CIFuzz, this task is similar to CIFuzz.
55 be interactive, it is meant to be long-lasting and generally is more similar to
[all …]
/external/brotli/.github/workflows/
Dfuzz.yml5 runs-on: ubuntu-latest
7 - name: Build Fuzzers
8 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
10 oss-fuzz-project-name: 'brotli'
11 dry-run: false
12 - name: Run Fuzzers
13 uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
15 oss-fuzz-project-name: 'brotli'
16 fuzz-seconds: 600
17 dry-run: false
[all …]
/external/capstone/.github/workflows/
Dfuzz.yml5 runs-on: ubuntu-latest
7 - name: Build Fuzzers
8 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
10 oss-fuzz-project-name: 'capstone'
11 dry-run: false
12 - name: Run Fuzzers
13 uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
15 oss-fuzz-project-name: 'capstone'
16 fuzz-seconds: 600
17 dry-run: false
[all …]
/external/pcre/.github/workflows/
Dcifuzz.yml5 runs-on: ubuntu-latest
7 - name: Build Fuzzers
9 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
11 oss-fuzz-project-name: 'pcre2'
12 dry-run: false
13 - name: Run Fuzzers
14 uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
16 oss-fuzz-project-name: 'pcre2'
17 fuzz-seconds: 300
18 dry-run: false
[all …]
/external/harfbuzz_ng/.github/workflows/
Dcifuzz.yml5 runs-on: ubuntu-latest
7 - name: Build Fuzzers
9 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
11 oss-fuzz-project-name: 'harfbuzz'
12 dry-run: false
13 - name: Run Fuzzers
14 uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
16 oss-fuzz-project-name: 'harfbuzz'
17 fuzz-seconds: 600
18 dry-run: false
[all …]
/external/gson/.github/workflows/
Dcifuzz.yml5 runs-on: ubuntu-latest
7 - name: Build Fuzzers
9 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
11 oss-fuzz-project-name: 'gson'
12 dry-run: false
14 - name: Run Fuzzers
15 uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
17 oss-fuzz-project-name: 'gson'
18 fuzz-seconds: 600
19 dry-run: false
[all …]
/external/libavc/.github/workflows/
Dcifuzz.yml5 runs-on: ubuntu-latest
7 - name: Build Fuzzers
9 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
11 oss-fuzz-project-name: 'libavc'
13 - name: Run Fuzzers
14 uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
16 oss-fuzz-project-name: 'libavc'
18 fuzz-seconds: 600
19 - name: Upload Crash
20 uses: actions/upload-artifact@v3
/external/libusb/.github/
Dcifuzz.yml5 runs-on: ubuntu-latest
7 - name: Build Fuzzers
9 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
11 oss-fuzz-project-name: 'libusb'
12 dry-run: false
14 - name: Run Fuzzers
15 uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
17 oss-fuzz-project-name: 'libusb'
18 fuzz-seconds: 600
19 dry-run: false
[all …]
/external/libbpf/.github/workflows/
Dcifuzz.yml1 ---
2 # https://google.github.io/oss-fuzz/getting-started/continuous-integration/
7 - master
10 - master
13 runs-on: ubuntu-latest
16 fail-fast: false
20 - name: Build Fuzzers (${{ matrix.sanitizer }})
22 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
24 oss-fuzz-project-name: 'libbpf'
25 dry-run: false
[all …]
/external/flac/.github/workflows/
Dcifuzz.yml6 - master
7 - 1.3.x
10 runs-on: ubuntu-latest
12 fail-fast: false
16 - name: Build Fuzzers (${{ matrix.sanitizer }})
18 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
20 oss-fuzz-project-name: 'flac'
23 - name: Run Fuzzers (${{ matrix.sanitizer }})
24 uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
26 oss-fuzz-project-name: 'flac'
[all …]
/external/selinux/.github/workflows/
Dcifuzz.yml1 ---
6 - master
9 - master
12 runs-on: ubuntu-latest
15 fail-fast: false
19 - name: Build Fuzzers (${{ matrix.sanitizer }})
21 uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
23 oss-fuzz-project-name: 'selinux'
24 dry-run: false
25 allowed-broken-targets-percentage: 0
[all …]
/external/cronet/testing/libfuzzer/
Dfuzzing_browsertests.md11 to fuzz a larger, more complex set of Chromium code, we usually need an entire
12 browser process environment around us. The browser process takes seconds to
15 We now have an experimental 'in process fuzz test' framework which attempts to:
17 * Execute lots of fuzz cases in that pre-existing browser.
18 This _may_ amortize the start up cost sufficiently to make such coverage-guided
22 # Writing an in process fuzz case
26 must override the `Fuzz` method. You'll find that your base class inherits
32 # Running such an in process fuzz case
41 `my_fuzzer /tmp/corpus -rss_limit_mb=81920`
45 out-of-process co-ordinator.
[all …]

12345