* Refactoring gcb libraries for external use
* Few changes done, a couple more left
* Fixed linting/formatting issues + other changes requested
* Fixing import order
* Fixing import order
* license header change
* Undo
Co-authored-by: Kabeer Seth <kabeerseth@google.com>
* Add wasm-tools repository to wasmtime project
This commit expands the fuzzers run under the Wasmtime project to
include those in the https://github.com/bytecodealliance/wasm-tools
repository. This includes various parsing for utilities used by Wasmtime
itself but also generally useful for other Rust projects! The
maintainers of the wasm-tools repository are also all currently all on
the notification list for Wasmtime fuzz bugs as well.
* Load all corpuses from wasmtime-libfuzzer-corpus
* fixing Dockerfile for libpng-proto
* adding json proto, LPM, and fuzz target for jsoncpp
* adding vanilla fuzzer back in
* fixing weird spacing in build script + taking out unneedef header file
* adding settings field and passing all of json_str
* adding license headers
* refactoring settings field
* fixing compile issue
* fixing MSan issue, changing license to 2020, and using iterator instead of pointers
* passing pointers more understandably to parse
* taking out unecessary assign
Co-authored-by: Danny Halawi <dhalawi@google.com>
* Add spanner emulator project
* Adding auto_css for Sneha and myself
* Adding dockerfile and build.sh files
* Further fixes for OSS-Fuzz integration
* Update build.sh
* Cleaning up commented code in build.sh
* Fuzzing branch merged with main in the emulator repo, modified dockerfile to clone main now instead of the branch.
* Updating build.sh to copy the binaries to out
* Cleaning up build.sh by removing Envoy specific comments, removed dictionary code as no corpus exists yet
* Updating yaml to include the memory sanitizer
* Build.sh should now copy fuzzing binaries properly to , adding fuzzing_enginers parameter to yaml to bypass AFL timeout for now.
Co-authored-by: Jonathan Volfson <volfson@google.com>
Co-authored-by: Oliver Chang <oliverchang@users.noreply.github.com>
* Base image builder
* Forgot to run formatter
* Fixing lint issues and removing unused imports
* Adding missing newline
* Refactoring code
* Fixing linting errors and changing name of cloud function entry
* Adding license header to build_base_images
* Changed logging and print_function
Co-authored-by: Kabeer Seth <kabeerseth@google.com>
* Add a working skeleton for OpenEXR fuzzers.
* added openexr fuzzers, updated build script to include them
* cleaned up bash loop
* replace "/work" with in build.sh
* Reformat CMake settings, and also prevent building utils and examples.
* Reformat and change names in build.sh.
* Omit the version prefix when building OpenEXR and IlmBase libraries.
* Correct the contact addresses for OpenEXR.
Co-authored-by: Ravi Jotwani <rjotwani@google.com>
This PR, integrates the new feature that allows users to specify their own schedules via project.yaml.
Parameter 'schedule : value' will dictate how many times a day should the project be built, i.e if value = 2
Then project will be built twice a day starting at 6 and interval 24/2 = 12 so 6:00 and 18:00
if parameter is unavailable DEFAULT_SCHEDULE = '0 6 * * *' i.e 6:00 will be used.
The cloud functions creates individual scheduler jobs for each project, with the name project_name + '-scheduler', and subscribes it to the topic 'request_build' with payload message 'project_name' which will be used by the next cloud function to request build for this project.
Co-authored-by: Kabeer Seth <kabeerseth@google.com>
Currently, coverage builds fail on step 3 with:
```
Step #3: + rsync -avLkR --include '*.h' --include '*.cc' --include '*.hpp' --include '*.cpp' --include '*.c' --include '*/' --exclude '*' /tmp /workspace/out/coverage
Step #3: sending incremental file list
Step #3: symlink has no referent: "/tmp/tmp.BOH6TAB62E/ares/include/ares_build.h"
Step #3: symlink has no referent: "/tmp/tmp.BOH6TAB62E/ares/include/ares_dns.h"
Step #3: symlink has no referent: "/tmp/tmp.BOH6TAB62E/ares/include/ares.h"
Step #3: symlink has no referent: "/tmp/tmp.BOH6TAB62E/ares/include/ares_rules.h"
Step #3: symlink has no referent: "/tmp/tmp.BOH6TAB62E/ares/include/ares_version.h"
Step #3: symlink has no referent: "/tmp/tmp.BOH6TAB62E/include/sha1.c"
Step #3: symlink has no referent: "/tmp/tmp.BOH6TAB62E/include/gcm_nohw.c"
Step #3: symlink has no referent: "/tmp/tmp.BOH6TAB62E/include/digests.c"
...
```
Just exclude these files. Doubt they matter to us.
Ref: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=23621&q=esp-v2&can=2
Signed-off-by: Teju Nareddy <nareddyt@google.com>
* syzkaller: update go get invocation
The way to checkout the repo has changed.
Fixes: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21994
* [syzkalle] Fix paths passed to `compile_fuzzer` function.
Co-authored-by: Max Moroz <mmoroz@chromium.org>
* [libspng] Fetch zlib in Dockerfile
This step has been moved from the build script: c35e509f04
* Update Dockerfile
* Update Dockerfile
* dummy commit
* Update Dockerfile
* dummy commit
* dummy commit
* Adding deploy.sh and restructuring directory
* Integrating review changes
* Passed project id as an argument to each command
Co-authored-by: Kabeer Seth <kabeerseth@google.com>
* libzmq: use build script from upstream repository
In order to avoid having to send PRs every time we change something, simply
maintain the build script in the upstream repository, and change build.sh
to a one-line call.
* libzmq: clone corpora and dictionary repository
Abhishek Arya