- 21 Dec, 2020 1 commit
-
-
This change makes it possible to build with newer versions of gcc without warnings. There were two warnings issued: * gcc 8 added [`-Wstringop-truncation`](https://developers.redhat.com/blog/2018/05/24/detecting-string-truncation-with-gcc-8/), which warns if a call to `strncpy(3)` is prone to accidentally truncating the destination string, since `strncpy(3)` does NOT add a terminating `NULL` if the destination buffer is not large enough to hold the input. This change uses the pattern suggested in https://us-cert.cisa.gov/bsi/articles/knowledge/coding-practices/strncpy-and-strncat to fix the locations flagged by gcc. * There was a potentially uninitialized access of `dest` in `fs_copy`.
lhchavez committed
-
- 14 Sep, 2020 1 commit
-
-
Philipp committed
-
- 09 Sep, 2020 1 commit
-
-
Philipp committed
-
- 05 Jun, 2020 1 commit
-
-
Edward Thomson committed
-
- 04 Jun, 2020 1 commit
-
-
Edward Thomson committed
-
- 03 Jun, 2020 2 commits
-
-
Add an output abstraction layer, with a single output format, "clap", the clar protocol, which is the current output format for clar.
Edward Thomson committed -
Edward Thomson committed
-
- 02 Jun, 2020 4 commits
-
-
Edward Thomson committed
-
Similar to how clar has used `/bin/cp` to copy files, it's used `/bin/rm` to remove them. This has similar deficiencies; meaning that leaks is noisy and it's slow. Move it to an internal function.
Edward Thomson committed -
Edward Thomson committed
-
clar has historically shelled out to `/bin/cp` to copy test fixtures into a sandbox. This has two deficiencies: 1. It's slower than simply opening the source and destination and copying them in a read/write loop. On my Mac, the `/bin/cp` based approach takes ~2:40 for a full test pass. Using a read/write loop to copy the files ourselves takes ~1:50. 2. It's noisy. Since the leak detector follows fork/exec, we'll end up running the leak detector on `/bin/cp`. This would be fine, except that the leak detector spams the console on startup and shutdown, so it adds a _lot_ of additional information to the test runs that is useless. By not forking and using this internal system, we see much less output.
Edward Thomson committed
-
- 05 Jul, 2019 1 commit
-
-
We use the `__LINE__` macro in several places throughout clar to allow easier traceability when e.g. a test fails. While `__LINE__` is of type `size_t`, the clar functions all accept an integer and thus may loose precision. While unlikely that any file in our codebase will exceed a linecount of `INT_MAX`, let's convert it anyway to silence any compiler warnings.
Patrick Steinhardt committed
-
- 06 Sep, 2018 6 commits
-
-
Windows lacks %F and %T formats for strftime. Expand them to the year/month/day and hour/minute/second formats, respectively.
Edward Thomson committed -
Remove the global summary filename and file pointer; pass them in to the summary functions as needed. Error check the results of buffered I/O calls.
Edward Thomson committed -
Accept an (optional) value for the summary filename. Continues to default to summary.xml.
Edward Thomson committed -
Edward Thomson committed
-
Etienne Samson committed
-
This makes it possible to keep track of every test status (even successful ones), and their errors, if any.
Etienne Samson committed
-
- 15 Jun, 2018 1 commit
-
-
Nika Layzell committed
-
- 25 Apr, 2018 1 commit
-
-
Matt Keeler committed
-
- 13 Nov, 2017 1 commit
-
-
motivation: (for someone new to the tests) it's puzzling to find the odd 'S' interspersed in the test output proposed alternative test output (extract): $ cmake --build . && ./libgit2_clar -srepo -v ... Loaded 340 suites: Started (test status codes: OK='.' FAILURE='F' SKIPPED='S') repo::config... repo::discover.......... repo::env. repo::getters... repo::hashfile.. repo::head...................... repo::headtree.... repo::init.........................S repo::message.. repo::new.. repo::open............. repo::pathspec.......... repo::reservedname..... repo::setters..... repo::shallow.... repo::state.............
Christine Poerschke committed
-
- 29 Jun, 2015 1 commit
-
-
Edward Thomson committed
-
- 22 Jun, 2015 1 commit
-
-
Support hierarchical test resource data, such that you can have `tests/resources/foo/bar` and move the `bar` directory in as a fixture. Calling `cl_fixture_sandbox` on a path that is not directly beneath the test resources directory succeeds, placing that directory into the test fixture. (For example, `cl_fixture_sandbox("foo/bar")` will sandbox the `foo/bar` directory as `bar`). Add support for cleaning up directories created this way, by only cleaning up the basename (in this example, `bar`) from the fixture directory.
Edward Thomson committed
-
- 24 Oct, 2014 1 commit
-
-
Edward Thomson committed
-
- 02 Apr, 2014 1 commit
-
-
Vicent Marti committed
-
- 28 Mar, 2014 1 commit
-
-
Edward Thomson committed
-
- 31 Jan, 2014 1 commit
-
-
Russell Belfer committed
-
- 14 Nov, 2013 1 commit
-
-
Ben Straub committed
-