| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
|
|
| |
This is needed for projects that mix both rust and c/c++.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Bumps [httplib2](https://github.com/httplib2/httplib2) from 0.11.3 to 0.18.0.
- [Release notes](https://github.com/httplib2/httplib2/releases)
- [Changelog](https://github.com/httplib2/httplib2/blob/master/CHANGELOG)
- [Commits](https://github.com/httplib2/httplib2/compare/v0.11.3...v0.18.0)
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add another maintainer to libzmq's CC list
* Enable UBSAN for libzmq
* libzmq: disable afl fuzzer, CI fails
* libsodium: do not let libsodium's autogen.sh download files from gnu.org
There is no sanity check and if the download fails because gnu.org is down
the build fails with unhelpful errors
|
|
|
|
|
| |
This is necessary for the bisector to be able to build older revisions.
Print a warning instead.
|
|
|
| |
This enables not only the binaryen-using fuzz targets, but also the peepmatic fuzz targets (which is necessary after https://github.com/bytecodealliance/wasmtime/pull/1727).
|
|
|
| |
Closes https://github.com/google/oss-fuzz/issues/3732
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* Parse project language and use in infra/helper.py
* Fix exception message.
|
| |
|
|
|
|
|
|
|
|
| |
* Simplify rust project setup.
- Add rust and cargo-fuzz in base builder.
- Set RUSTC_BOOSTRAP to make ASan available.
- Set RUSTFLAGS and C,CXXFLAGS properly.
|
|
|
|
|
| |
Relates to https://gitlab.labs.nic.cz/knot/knot-dns/-/commit/d4ec3a3aa8b7e2ba4d196e2f7984173069e3d91b
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22191
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* [Prometheus] Initial integration
* Added missing dash in project.yaml
|
|
|
|
|
| |
Build is failing.
This reverts commit 564354a8346d6ee0205fd6365c5eb55259aaef3c.
|
|
|
|
|
|
|
| |
[rdkit] Speculative fix for build failure
Build was failing on GCB because WORKDIR is parsed, changed and then restored
by gcb build script. Parsing assumed that only one WORKDIR call is made.
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Start fuzzing ClickHouse project
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix clang updating script to actually update clang based on Chrome's
With this change, clang (llvm-project) will be updated from:
e84b7a5fe230e42b8e6fe451369874a773bf1867
to Chrome's current version:
99ac9ce7016d701b43b8f0c308dc3463da57d983.
This commit fixes two bad bugs:
1. Using the output of a command instead of the return code.
2. Using ! to determine whether the command succeeded ! in bash
will do the same thing for 0 and 1.
These bugs were hidden by OUR_LLVM_REVISION which we traditionally
set to the last commit we rolled back to. If this were a comment
instead of stored as a variable that is not supposed to be used
unless FORCE_OUR_REVISION is set, this bug probably could have
been caught earlier. Instead, the code always used the value
provided by this variable.
Fixes https://github.com/google/oss-fuzz/issues/3805
|
|
|
|
| |
s/allowed_broken_targets_percentage/allowed-broken-targets-percentage/ (#3803)
|
| |
|
|
|
|
|
|
|
|
|
| |
* [libtheora] Update upstream repository url
* [speex] Update upstream repository url
* [tremor] Update upstream repository url
* [vorbis] Update upstream repository url
|
|
|
|
|
|
|
|
| |
Currently we use Github action's inputs as inputs to cifuzz.
This means we need to do an extra step to convert each input into
an env var so our scripts can actually use it.
This is pretty bug prone and unnecessary, we should probably
get rid of this abstraction and switch to encouraging devs to set
the env vars directly.
|
| |
|
|
|
|
|
| |
Fixes: 22072
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Signed-off-by: Asra Ali <asraa@google.com>
|
| |
|
| |
|
|
|
| |
Signed-off-by: Eduardo Silva <edsiper@gmail.com>
|
| |
|