summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* coverityethomson/nightliesEdward Thomson2018-07-291-3/+3
|
* coverityEdward Thomson2018-07-291-1/+1
|
* coverityEdward Thomson2018-07-291-2/+6
|
* ci: run coverity during a nightly build runEdward Thomson2018-07-281-0/+22
|
* ci: run coverity from travis's cronEdward Thomson2018-07-282-14/+3
| | | | | | Instead of trying to run coverity builds during the regular PR process, run them during a regularly scheduled cron process. These only need to run nightly, so it makes sense to bring them out of the PR process.
* ci: remove unused old ci scriptsEdward Thomson2018-07-285-150/+0
|
* ci: move travis to the new scriptsEdward Thomson2018-07-285-19/+39
|
* ci: move appveyor to new scriptsEdward Thomson2018-07-272-61/+21
|
* ci: use a single setup script for mingwEdward Thomson2018-07-263-26/+13
|
* ci: use docker containers from libgit2 accountEdward Thomson2018-07-261-8/+8
|
* ci: perform clang builds on LinuxEdward Thomson2018-07-263-7/+77
|
* ci: dissociate test from leaks processEdward Thomson2018-07-261-2/+1
| | | | | | The leaks process is not good about handling children. Ensure that its child is `nohup`ed so that the grandparent shell won't wait for it to exit.
* ci: some additional debuggingEdward Thomson2018-07-261-0/+8
|
* ci: enable leak checking on osxEdward Thomson2018-07-263-0/+5
|
* ci: msvc leak-checkingEdward Thomson2018-07-262-5/+4
|
* ci: xcode leaks leak-checkingEdward Thomson2018-07-261-0/+4
|
* buf tests: allocate a smaller size for the oomEdward Thomson2018-07-261-3/+15
| | | | | | | | | | | On Linux (where we run valgrind) allocate a smaller buffer, but still an insanely large size. This will cause malloc to fail but will not cause valgrind to report a likely error with a negative-sized malloc. Keep the original buffer size on non-Linux platforms: this is well-tested on them and changing it may be problematic. On macOS, for example, using the new size causes `malloc` to print a warning to stderr.
* ci: valgrind leak-checkingEdward Thomson2018-07-262-7/+28
|
* ci: introduce vsts buildsEdward Thomson2018-07-262-0/+135
|
* ci: scripts to setup mingw build environmentEdward Thomson2018-07-262-0/+40
|
* ci: set up a macos hostEdward Thomson2018-07-261-0/+6
| | | | Script to set up dependencies on a macOS build system.
* ci: setup a linux hostEdward Thomson2018-07-261-0/+8
| | | | Sets up a linux host to prepare for a build.
* ci: improved flexibility for citest.shEdward Thomson2018-07-261-67/+125
| | | | Refactor citest.sh to enable local testing by developers.
* ci: refactor unix ci build/test scriptsEdward Thomson2018-07-262-0/+138
|
* ci: move tests into citest.ps1Edward Thomson2018-07-262-19/+45
| | | | Add citest.ps1 PowerShell script to run the tests.
* ci: Windows PowerShell build scriptEdward Thomson2018-07-261-0/+50
|
* tests: simplify cmake test configurationEdward Thomson2018-07-263-14/+13
| | | | | | | | | Simplify the names for the tests, removing the unnecessary "libgit2-clar" prefix. Make "all" the new default test run, and include the online tests by default (since HTTPS should always be enabled). For the CI tests, create an offline-only test, then the various online tests.
* Merge pull request #4739 from pks-t/pks/mbedtls-unused-variableEdward Thomson2018-07-261-4/+0
|\ | | | | mbedtls: remove unused variable "cacert"
| * mbedtls: remove unused variable "cacert"Patrick Steinhardt2018-07-261-4/+0
|/ | | | | | | | | In commit 382ed1e87 (mbedtls: load default CA certificates, 2018-03-29), the function `git_mbedtls_stream_global_init` was refactored to call out to `git_mbedtls__set_cert_location` instead of setting up the certificates itself. The conversion forgot to remove the now-unused "cacert" variable, which is now only getting declared to be free'd at the end of the function. Remove it.
* Merge pull request #4732 from libgit2/ethomson/leaksEdward Thomson2018-07-233-9/+34
|\ | | | | Squash some leaks
| * mbedtls: free stream on shutdownethomson/leaksEdward Thomson2018-07-201-0/+1
| |
| * mbedtls: make ciphers_list a static arrayEdward Thomson2018-07-201-10/+10
| | | | | | | | | | Instead of allocating the ciphers_list, make it a static array. This prevents us from leaking it or having to manage its memory.
| * mbedtls: free ciphers_listEdward Thomson2018-07-201-0/+2
| |
| * mbedtls: check allocationsEdward Thomson2018-07-201-1/+14
| |
| * push tests: deeply free the specsEdward Thomson2018-07-201-1/+1
| | | | | | | | Don't just free the spec vector, also free the specs themselves.
| * push tests: deeply free the push statusEdward Thomson2018-07-201-2/+6
| | | | | | | | | | Don't just free the push status structure, actually free the strings that were strdup'd into the struct as well.
| * smart subtransport: free url when resetting streamEdward Thomson2018-07-201-0/+5
|/ | | | Free the url field when resetting the stream to avoid leaking it.
* Merge pull request #4692 from tiennou/examples/checkoutPatrick Steinhardt2018-07-206-23/+309
|\ | | | | Add a checkout example
| * examples: add checkoutEtienne Samson2018-07-171-0/+235
| |
| * examples: add a helper for boolean-style optionsEtienne Samson2018-07-072-0/+28
| |
| * examples: make the refish resolution work with short OIDsEtienne Samson2018-07-071-3/+4
| |
| * examples: move refish resolution function in commonEtienne Samson2018-07-073-23/+29
| |
| * annotated_commit: make the refname accessibleEtienne Samson2018-07-072-0/+16
| | | | | | | | | | | | As git_annotated_commit seems to behave like cgit's refish, it's quite helpful to abstract away "targets" via git_annotated_commit_from_id/from_ref. As the former is accessible via git_annotated_commit_id, make the latter also available to users.
* | Merge pull request #4702 from tiennou/fix/coverityPatrick Steinhardt2018-07-2011-46/+54
|\ \ | | | | | | Assorted Coverity fixes
| * | tests: fix a relative pathname issueEtienne Samson2018-07-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | The path given to `git_index_add_bypath` is relative to the root of the repository. That `describe/file` path is relative to the root of the sandbox directory, hence if I add the missing `cl_git_pass` I rightfully get an error that `$SANDBOX/describe/describe/file doesn't exist`. The path is thus changed to be made relative to the repository, which makes the failure go away and "restore" the test.
| * | tests: add missing cl_git_pass to testsEtienne Samson2018-07-066-24/+24
| | | | | | | | | Reported by Coverity, CID 1393678-1393697.
| * | smart: don't dereference a NULL pkt pointerEtienne Samson2018-07-062-12/+15
| | | | | | | | | | | | | | | | | | | | | By clarifying what detect_caps returns on empty/missing packet, we can be sure there are actually refs to process. The old code could blindly dereference `first`, which might have been NULL. Reported by Coverity, CID 1393614
| * | smart: clarify error handling in git_smart__connectEtienne Samson2018-07-061-8/+9
| | |
| * | submodule: don't leak memory when failing to insert the namesEtienne Samson2018-07-061-1/+2
| | | | | | | | | Reported by Coverity, CID 1393237
| * | tests: mailmap/parsing: add a missing cl_git_passEtienne Samson2018-07-061-1/+1
| | | | | | | | | Reported by Coverity, CID 1393483
View Lorry Controller Status