Age | Commit message (Collapse) | Author |
|
|
|
Don't delete unaffected fuzzers and don't do bad build check.
|
|
Also clean up the external action definitions:
- Set default values for the storage repo branches.
- Remove storage repo options from build_fuzzers.
|
|
Delete our python implementation which appears buggy and will be annoying to maintain.
Fixes: https://github.com/google/oss-fuzz/issues/6526
|
|
|
|
Fixes: #6525
Depends on: #6530
|
|
We will use this to upload artifacts in the future.
|
|
Otherwise incomplete builds may be uploaded.
Fixes: https://github.com/google/oss-fuzz/issues/6529
Related: https://github.com/google/oss-fuzz/issues/6525
|
|
Fixes #6326.
|
|
|
|
|
|
Fixes #6376.
|
|
Part of #6326.
|
|
build_and_push_test_images. (#6359)
|
|
|
|
* [cifuzz] Fix bug caused by Ubuntu upgrade.
systemd-detect-virt isn't being found.
* fix
|
|
Handle upgrade to Ubuntu 20.04
1. Don't do any special handling for MSAN anymore. It isn't needed.
2. Don't do any special handling for msan-libs-builder it doesn't
exist anymore.
Related: https://github.com/google/oss-fuzz/issues/6180
|
|
The current way adds a lot of ordering assumptions, and doesn't fit too
well with parallel batch fuzzing either. Add a "upload-build" boolean action
input that can be added to "build_fuzzers" to upload latest builds
instead.
Builds are now uploaded by commit hash, rather than a fixed "latest" name.
ClusterFuzzLite's download_latest_build will check the last 3 commits and download the
first available build by git hash.
|
|
(#6198)
Also rename mock_ functions to have impl suffix so we can use mock_ in place of mocked_
|
|
Fixes: #6064
|
|
|
|
|
|
Fixes: #5926
|
|
Do this only where it makes sense. For example, since CIFuzz doesn't
support dataflow, maintain a separate source of truth.
|
|
|
|
|
|
This removes need for non-OSS-Fuzz users to fake using OSS-Fuzz.
Fixes: #6129
|
|
|
|
In hindsight, it doesn't have a lot to do with the rest of
config_utils. And config_utils is getting crowded.
|
|
This test doesn't really do diffing or affected fuzzers properly.
Nor does it check the workspace for existence of certain things, nor
does check the filesystem for proof things happened. It is still
a WIP.
|
|
* [cifuzz] Create validate method on BaseConfig
Use it to validate that either OSS_FUZZ_PROJECT_NAME
or BUILD_INTEGRATION_PATH is set.
Also use it to validate that workspace is set
(rather than duplicate code).
Add tests.
* Use env var hack to bypass valdiation
* fix
* fix
* fmt
* fix
* tmp
* fix
|
|
We shouldn't delete it, because we need to use it again.
This saves about 13 seconds per run.
Fixes: #5982
|
|
Don't try to find unaffected fuzzers by diffing against a base commit as
they don't exist in those contexts.
For #6053.
|
|
|
|
Also delete useless TODOs.
|
|
Don't assume that path is relative to workspace if it is not absolute.
Only make this assumption on GitHub where it will always be true.
Also, add tests.
|
|
This should mostly complete support for affected fuzzers for external users.
This implementation is still imperfect however.
It relies on the name of the repo being the same as the name of the directory in $SRC/ that the repo is checked out in
(i.e. repo must be checked out in $SRC/$REPO_NAME).
|
|
Fixes: #6119
Also add more tests for continuous_integration module.
|
|
|
|
|
|
|
|
It doesn't really fit into docker.
|
|
This can be used by non-github users.
Related: #6100
|
|
|
|
- Add storage-repo, storage-repo-branch, and
storage-repo-branch-coverage fields to the actions, to indicate that
the Git filestore should be used.
- The CI provided filestore is still used for crashes and builds.
- Replace generic Filestore.upload_directory with typed upload methods
which matches the download methods.
- Rename upload_latest_build to upload_build to make it more generic.
- Make artifact name prefixes an implementation detail of the store.
For #6052.
|
|
|
|
This can be useful for artifacts we want to upload that we know
do not need to be tarred, such as crashes. It's important not
to tar these because they will need to be viewed by users.
|
|
This will be used for testing and can be moved elsewhere later.
|
|
Previously, the downloaded build was uploaded instead of the new build.
This regression was introduced when the big workspace change was made.
Also, add more logging.
|
|
To avoid issues like #6087 before they land.
|