delta/libgit2.git/tests/checkout/tree.c, branch ethomson/https_proxy github.com: libgit2/libgit2.git object_type: use new enumeration names 2018-12-01T11:54:57+00:00 Edward Thomson ethomson@edwardthomson.com 2018-11-28T14:26:57+00:00 168fe39bea3368972a8b1a33d5908e73bc790c18 Use the new object_type enumeration names within the codebase. 
Use the new object_type enumeration names within the codebase.
index: use new enum and structure names 2018-12-01T10:46:44+00:00 Edward Thomson ethomson@edwardthomson.com 2018-11-28T13:31:06+00:00 18e71e6d597abe6c7feb666429c921bd19dc0ba8 Use the new-style index names throughout our own codebase. 
Use the new-style index names throughout our own codebase.
Merge pull request #4702 from tiennou/fix/coverity 2018-07-20T10:56:49+00:00 Patrick Steinhardt ps@pks.im 2018-07-20T10:56:49+00:00 0652abaaeaff768e78a65464e59bd1896ce2f6ce Assorted Coverity fixes 
Assorted Coverity fixes
 treewide: remove use of C++ style comments 2018-07-13T06:25:12+00:00 Patrick Steinhardt ps@pks.im 2018-06-25T09:56:52+00:00 9994cd3f0ffcd7b28d26c82ecb6564bc4072dc2a C++ style comment ("//") are not specified by the ISO C90 standard and thus do not conform to it. While libgit2 aims to conform to C90, we did not enforce it until now, which is why quite a lot of these non-conforming comments have snuck into our codebase. Do a tree-wide conversion of all C++ style comments to the supported C style comments to allow us enforcing strict C90 compliance in a later commit. 
C++ style comment ("//") are not specified by the ISO C90 standard and
thus do not conform to it. While libgit2 aims to conform to C90, we did
not enforce it until now, which is why quite a lot of these
non-conforming comments have snuck into our codebase. Do a tree-wide
conversion of all C++ style comments to the supported C style comments
to allow us enforcing strict C90 compliance in a later commit.
tests: add missing cl_git_pass to tests 2018-07-06T20:24:21+00:00 Etienne Samson samson.etienne@gmail.com 2018-07-01T10:04:27+00:00 8455a2709f8c2fabf0df775a193b9ef72bb21e43 Reported by Coverity, CID 1393678-1393697. 
Reported by Coverity, CID 1393678-1393697.
 checkout: FORCE doesn't halt on dirty index 2018-06-29T13:54:28+00:00 Edward Thomson ethomson@edwardthomson.com 2018-06-18T17:28:08+00:00 5e26391a2579062bdf5d6f0efe6b03f78d28f825 If the index is dirty, allow `GIT_CHECKOUT_FORCE` to obliterate unsaved changes. This is in keeping with its name and description. 
If the index is dirty, allow `GIT_CHECKOUT_FORCE` to obliterate unsaved
changes.  This is in keeping with its name and description.
index: commit the changes to the index properly 2018-06-29T13:54:28+00:00 Edward Thomson ethomson@edwardthomson.com 2017-11-17T00:19:07+00:00 b242cdbf1e1dd2cc9e26e0085a20230ff34d156b Now that the index has a "dirty" state, where it has changes that have not yet been committed or rolled back, our tests need to be adapted to actually commit or rollback the changes instead of assuming that the index can be operated on in its indeterminate state. 
Now that the index has a "dirty" state, where it has changes that have
not yet been committed or rolled back, our tests need to be adapted to
actually commit or rollback the changes instead of assuming that the
index can be operated on in its indeterminate state.
checkout tests: validate GIT_CHECKOUT_NO_REFRESH 2018-06-29T13:54:26+00:00 Edward Thomson ethomson@edwardthomson.com 2018-06-18T15:14:26+00:00 55a966068d26db2287d32d8cc8347c31df90f02a Add tests that ensure that we re-read the on-disk image by default during checkout, but when the `GIT_CHECKOUT_NO_REFRESH` option is specified, we do _not_ re-read the index. 
Add tests that ensure that we re-read the on-disk image by default
during checkout, but when the `GIT_CHECKOUT_NO_REFRESH` option is
specified, we do _not_ re-read the index.
Convert usage of `git_buf_free` to new `git_buf_dispose` 2018-06-10T17:34:37+00:00 Patrick Steinhardt ps@pks.im 2018-02-08T11:14:48+00:00 ecf4f33a4e327a91496f72816f9f02d923e5af05 






tests: status::worktree: indicate skipped tests on Win32
2018-01-03T11:50:38+00:00

Patrick Steinhardt
ps@pks.im

2017-06-07T08:59:03+00:00

72c28ab011759dce113c2a0c7c36ebcd56bd6ddf

Some function bodies of tests which are not applicable to the Win32
platform are completely #ifdef'd out instead of calling `cl_skip()`.
This leaves us with no indication that these tests are not being
executed at all and may thus cause decreased scrutiny when investigating
skipped tests. Improve the situation by calling `cl_skip()` instead of
just doing nothing.





Some function bodies of tests which are not applicable to the Win32
platform are completely #ifdef'd out instead of calling `cl_skip()`.
This leaves us with no indication that these tests are not being
executed at all and may thus cause decreased scrutiny when investigating
skipped tests. Improve the situation by calling `cl_skip()` instead of
just doing nothing.