summaryrefslogtreecommitdiff
path: root/tests/apply/fromfile.c
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #4847 from noahp/noahp/null-arg-fixesEdward Thomson2018-11-181-1/+2
|\ | | | | tests: 🌀 address two null argument instances
| * tests: address two null argument instancesNoah Pendleton2018-11-131-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Handle two null argument cases that occur in the unit tests. One is in library code, the other is in test code. Detected by running unit tests with undefined behavior sanitizer: ```bash # build mkdir build && cd build cmake -DBUILD_CLAR=ON -DCMAKE_C_FLAGS="-fsanitize=address \ -fsanitize=undefined -fstack-usage -static-libasan" .. cmake --build . # run with asan ASAN_OPTIONS="allocator_may_return_null=1" ./libgit2_clar ... ............../libgit2/src/apply.c:316:3: runtime error: null pointer \ passed as argument 1, which is declared to never be null ...................../libgit2/tests/apply/fromfile.c:46:3: runtime \ error: null pointer passed as argument 1, which is declared to never be null ```
* | apply: introduce a hunk callbackEdward Thomson2018-11-051-1/+1
|/ | | | | Introduce a callback to patch application that allows consumers to cancel hunk application.
* Convert usage of `git_buf_free` to new `git_buf_dispose`Patrick Steinhardt2018-06-101-3/+3
|
* git_patch_parse_ctx: refcount the contextEdward Thomson2016-05-261-0/+1
|
* patch: `git_patch_from_patchfile` -> `git_patch_from_buffer`Edward Thomson2016-05-261-12/+13
|
* apply: test postimages that grow/shrink originalEdward Thomson2016-05-261-0/+42
| | | | | | | Test with some postimages that actually grow/shrink from the original, adding new lines or removing them. (Also do so without context to ensure that we can add/remove from a non-zero part of the line vector.)
* Introduce git_patch_options, handle prefixesEdward Thomson2016-05-261-37/+37
| | | | | Handle prefixes (in terms of number of path components) for patch parsing.
* apply: move patch data to patch_common.hEdward Thomson2016-05-261-1/+1
|
* patch: abstract patches into diff'ed and parsedEdward Thomson2016-05-261-0/+1
| | | | | | Patches can now come from a variety of sources - either internally generated (from diffing two commits) or as the results of parsing some external data.
* patch parsing: ensure empty patches are illegalEdward Thomson2016-05-261-0/+8
|
* patch parsing: parse binary patch filesEdward Thomson2016-05-261-55/+123
|
* patch application: apply binary patchesEdward Thomson2016-05-261-0/+27
| | | | | | Handle the application of binary patches. Include tests that produce a binary patch (an in-memory `git_patch` object), then enusre that the patch applies correctly.
* Patch parsing from patch filesEdward Thomson2016-05-261-0/+301