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
* fixing Dockerfile for libpng-proto
* Fixing Dockerfile so the LPM for giflib works
* Fixing Dockerfile so the LPM for xerces-c works
* taking out unneeded installations
Co-authored-by: Danny Halawi <dhalawi@google.com>
* [util-linux] cover mnt_table_parse_stream
Waiting for https://github.com/karelzak/util-linux/pull/1068
* temporarily point OSS-Fuzz to evverx/util-linux
* make sure it can be built with sanitizer=coverage
* added draco integration files
* wrote build file and Dockerfile for Draco
* split security-research-pocs fuzzer into four
* added project build to build.sh
* added more fuzzers
* fixed sanitizer flags
* removed commented code, combined fuzzers, fized build script
* changed to singular filenames, converted usage of random int to enum, changed buffer name, and fixed build script
* placed test files in memory instead of on disk, added asserts
Integrating the first cloud function i implemented which syncs the project list from github and uploads the list to cloud datastore, which will be used by another cloud function to request builds.
Co-authored-by: Kabeer Seth <kabeerseth@google.com>
* [libxml2] Two new fuzz targets
Enable HTML and XML Schema fuzzers.
* [libxml2] Compile missing source files
* [libxml2] Don't forget to build seed corpora
* added draco integration files
* wrote build file and Dockerfile for Draco
* added Apache 2 license header
* changed project maintainer, cleaned up draco_decoder_fuzzer, and set working directory in Dockerfile
* added a couple of fuzzers
* two more targets
* merged from upstream
* build point cloud encoding fuzzer, renamed quantization fuzzers
* added more fuzzers
* moved fuzzers and build script to https://github.com/google/draco, made the build script here execute the new one
Co-authored-by: Ravi Jotwani <rjotwani@google.com>
* QEMU: Add fuzz target build scripts
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
* QEMU: Disable AFL and MSan in project.yaml
We can't link against OSS-Fuzz' afl driver as it is not compiled with
-fPIC. Additionally, it appears that we trigger some false-positives
with MemorySanitizer, since we don't instrument all of the libraries.
Disable AFL and MemorySanitizer, for now.
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
* [opus] Build with -D_FORTIFY_SOURCE=0 to avoid msan false positives
Without this, a silk_memcpy call could resolve to __memcpy_chk,
which does not have an msan intercept, leading to false use-of-uninitialized-value errors.
* [opus] Consolidate cflags
* [opus] Fix typo
Nick Fitzgerald