| Commit message (Collapse) | Author | Age |
| |
|
|
|
| |
Co-authored-by: Martin Barbella <mbarbella@google.com>
|
| |
|
| |
|
|
|
| |
This reverts commit 65cd35731fc91fe700902ec6d0a31993bf4fe0ec.
|
| |
|
|
|
|
|
|
|
|
| |
[CIFuzz] Don't assume fuzzer output is ascii
This is wrong because the output can be arbitrary. Instead change
code that deals with the output to deal with bytes. The testcase,
which is derived from the output can be decoded as UTF-8 since it
will be a unix path.
|
|
|
|
|
| |
(#4523)" (#4525)
This reverts commit fa0c1b4c6d9f7d235ea297608e5cc434443aa7d8.
|
|
|
|
|
| |
(#4522)" (#4524)
This reverts commit 6fe03eafb557c631d598cf2391f737f34499cb8c.
|
|
|
|
|
| |
* SyntaxError: leading zeros in decimal integer literals are not permitted; use an 0o prefix for octal integers
* Placate pylint
|
|
|
| |
Python SyntaxError: leading zeros in decimal integer literals are not permitted; use an 0o prefix for octal integers
|
|
|
|
| |
Skia has seen some unhandled connection reset errors.
When we see these errors when downloading old OSS-Fuzz build, retry downloading it, since the error is likely transient.
|
|
|
|
|
|
| |
* Enables MSAN for Suricata
* Move rustup std lib download to base-builder
|
| |
|
|
|
| |
But do this after computing repo_url as that's still useful information.
|
|
|
| |
Fixes #4400
|
| |
|
|
|
|
|
|
|
|
| |
This is needed for CF to determine whether or not to allocate the
project on a higher end bot to run the blackbox fuzzer.
Previously this was keyed on the "none" entry under fuzzing_engines,
which wasn't very descriptive. This change also lets us do both blackbox
and greybox fuzzing in the same project, which will be done for quickjs.
|
|
|
|
|
|
|
|
|
|
|
| |
Coverage builds need to be special cased since they aren't specified
in sanitizers. Instead they are done for all C/C++ projects that
use libFuzzer.
Move all of this special casing to `should_build_coverage` and call that from
`should_build` so we have one place where we decide this.
Add tests as well.
Fixes: https://github.com/google/oss-fuzz/issues/4371
|
|
|
| |
'none' is used by projects like spidermonkey that use the JS fuzzer.
|
|
|
|
|
|
|
|
|
| |
(#4338). (#4367)
* [infra] Fix reproduce command invoking run_fuzzer for a single testcase (#4338).
* review feedback
* do not introduce new variable, rely on SKIP_SEED_CORPUS only
|
|
|
| |
Temporarily fixes #4348
|
|
|
|
|
| |
(#4351)" (#4352)
This reverts commit 7f8f5e0182ec994ed5b7340cdf90c532da1ee328.
|
|
|
| |
This reverts commit d1ddd259378933ab42966da3e6750612c3ec2de4.
|
| |
|
|
|
|
|
|
|
| |
* [infra] Upgrade reproduce command to re-use run_fuzzer functionality.
* fix a typo
* add missing quotes
|
|
|
|
|
| |
* [infra] Use 16 threads when building LLVM (#4270).
* update the comment
|
| |
|
|
|
|
|
|
|
| |
(#4301)
* [infra] Make bad_build_check to use run_fuzzer when testing startup crash.
* use SKIP_SEED_CORPUS=1
|
|
|
|
|
|
|
| |
only (#4284). (#4303)
* [infra][docs] Be more explicit about code coverage being supported for C/C++ only (#4284).
* fix typos and pass env variable
|
| |
|
|
|
|
|
|
|
| |
* Fix typo in project_sync.py
* line length
* format
|
| |
|
|
|
|
|
|
|
| |
* [infra] Add support for custom sanitizer options in run_fuzzer.
* address review feedback
* fix presubmit warnings
|
|
|
|
| |
Fix parse regex as per format change in
https://chromium.googlesource.com/chromium/src/tools/clang/+/e6863f878319bc31e7f454132b655251f9761fc2%5E%21/#F1
|
|
|
|
|
| |
The issue with 55d9a81 that caused it to be reverted by 3370f8f
was probably due to the build trigger on GCB being stale. I've
updated it so this commit should stick.
|
|
|
|
|
| |
This reverts commit 55d9a81cd799f34ffbd688766aef5f463c9aac73.
Closes https://github.com/google/oss-fuzz/issues/4262
|
|
|
|
|
| |
- Split into separate invocations for fuzzing, coverage, and badges.
- Also use threads to speed things up.
|
|
|
|
|
|
|
| |
Make CIFuzz building accept an env var `MANUAL_SRC_PATH` that points to a manually prepared checkout of the project-under-tests's source code. This allows projects like Skia which are not on OSS-Fuzz and/or need to make changes to the repo after checking out the right commit to use CIFuzz.
Note that for now we aren't supporting this in GitHub, so projects that need to modify the source after checkout can't use it until
we do support it.
Also, use the local copy of OSS-Fuzz when building cifuzz-base instead of cloning it from GitHub. This makes local debugging/development much easier since it allows one to use CIFuzz with local changes.
|
|
|
|
| |
- Deleted unused code.
- Consolidate some modules.
|
|
|
|
|
|
| |
- Remove gcb folder. Move the files that we still need into the
build/functions dir.
- Remove badge_images. They are now stored on GCS.
- Remove jenins configs.
|
|
|
|
|
| |
* Skipping fuzzing build when project is disabled
* Removing skip build and making it better
|
| |
|
|
|
|
| |
Clang now needs a newer cmake to build.
|
|
|
|
|
|
|
|
|
| |
* Adding msan builder to gcp
* Formatting changes
* Refactoring and reducing redundancy
* Moving msan builder entry point into base_images
|
|
|
|
| |
The single function for requesting all coverage builds was timing out.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Initial UI Change to display historical logs
* Minor changes
* More formatting changes
* Adding license header
* Changes, take a look Oliver
* Changes for handling empty build history/ no last successful build
* Reverting the logs folder path from /logs/log to /log
* Merged to latest master and other chnages to template
* Changing backend to reflect build history
* Fixing order of query
* Removed last build status
* More changes
* Adding unit tests and fixes found by unit testing
* Fixing lint errors
* Added more unit tests and fixed typos and formatting
* Fixing comment caps
* Minor formatting issue
Co-authored-by: Oliver Chang <oliverchang@users.noreply.github.com>
|
|
|
|
|
| |
Check for valid statuses rather than only excluding the WORKING status.
There are other failure statuses that need to be accounted for (e.g.
EXPIRED).
|
| |
|