aboutsummaryrefslogtreecommitdiff
path: root/projects/git
AgeCommit message (Collapse)Author
2021-08-26Reland [Ubuntu upgrade] Fix projects so they don't break with upgrade (#6313)jonathanmetzman
This reverts commit 878c32419cdf89457d1f1be616d4896fc2586160. Related: #6180
2021-08-26Revert "[Ubuntu upgrade] Fix projects so they don't break with upgrade. ↵Oliver Chang
(#6304)" (#6306) This reverts commit 5549d804b3640462549401597cfef382911b3933.
2021-08-25[Ubuntu upgrade] Fix projects so they don't break with upgrade. (#6304)jonathanmetzman
Fix projects so they don't break with upgrade. These fixes are likely not backwards compatible and will fail on Ubuntu 16.04. Related: #6180
2021-02-22Fix git build by ignoring leaks in build.sh (#5240)Andrzej Hunt
The oss-fuzz git ASAN build fails due to a leak inside git iself: the build script builds a copy of git, and then uses that binary to prepare the corpus - although the git invocation itself succeeds, ASAN causes the script to fail due to the leak: https://oss-fuzz-build-logs.storage.googleapis.com/log-2eee2921-1b3f-4dd8-a902-50474e8fed55.txt This was reproduced locally using: $ python infra/helper.py build_fuzzers --sanitizer address git Disabling leak checking for all invocations of git in the script is enough to avoid this failure, thus fixing the build. The leak itself is being fixed in git in the following commit (which is now in next, hence the build should be fixed by now): https://git.kernel.org/pub/scm/git/git.git/commit/?id=bf4bb9f9f5130a7b299f7810fb87a40cdd1bd8ee However, I still believe we should be disabling leak checking during the build script in this way because: 1. This issue persisted for close to one month before being fixed, and blocking oss-fuzz runs on a leak during the build process for that long seems counter-productive. 2. An alternative would be to use a pre-built copy of git to build the corpus (thus sidestepping ASAN in the first place), but IMHO installing git via the Dockerfile seems more wasteful AND it's unclear if that would have side effects (I'm not sure if the commit-graph format changes between versions).
2020-12-09Fill in main_repo for several projects. (#4816)Abhishek Arya
* Fill in main_repo for several projects. * Add some go repos.
2020-09-16[git] add team members to auto_ccs list (#4452)steadmon
2020-09-02[git] Add auto_ccs to project.yaml (#4406)steadmon
2020-07-06Update Dockerfiles (#4070)devtty1er
* Use LABEL in place of MAINTAINER * Remove LABEL maintainer from Dockerfiles
2020-03-10[presubmit] Enforce language attribute in project.yaml to be always set. (#3477)Max Moroz
* [presubmit] Enforce language attribute in projectt.yaml to be always set. * Update documentation, better presubmit check, new project template. * add docstring to templates.py * Add example values in the project.yaml template and remove python value for now * Add "project: c++" to 256 projects * format * Add labels and selective_unpack sections to the presubmit check * fix incorrect auto_ccs format in three projects * fix nss emails after rebase
2019-07-12Remove experimental bit for git project. (#2596)Abhishek Arya
2019-06-05[git] Fuzz against the upstream "next" branch. (#2488)steadmon
The next branch is where relatively-stable changes live while testing for stability. We should fuzz against this branch to give extra confidence that these patches are bug-free before they are merged into master.
2019-02-19[git] Add the new fuzz-commit-graph fuzzer. (#2170)steadmon
2018-12-04Use new FUZZ_CXXFLAGS when building git. (#2004)steadmon
This removes a ton of build warnings and prevents future build breakage in the case where incompatible CFLAGS / CXXFLAGS are required.
2018-11-15Don't install 'recommended' packages, to save on build time and image size. ↵steadmon
(#1957)
2018-11-09[git] Add basic config for git fuzzing. (#1938)steadmon
* Add basic config for git fuzzing. * Fix CFLAGS/CXXFLAGS issue when building Git fuzzers. * Build corpora from packfiles and add libfuzzer options.