kmx git

Commit	Date	Message
ce798b25	2018-07-04T10:56:56	tests: simplify cmake test configuration 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.
3a72b0e2	2018-04-03T12:31:35	appveyor: fix typo in registry key to disable DHE Commit 723e1e976 (appveyor: disable DHE to avoid spurious failures, 2018-03-29) added a workaround to fix spurious test failures due to a bug in Windows' SChannel implementation. The workaround only worked by accident, though, as the registry key was in fact mistyped. Fix the typo.
723e1e97	2018-03-29T13:35:27	appveyor: disable DHE to avoid spurious failures Our CI builds have intermittent failures in our online tests, e.g. with the message "A provided buffer was too small". This is not a programming error in libgit2 but rather an error in the SChannel component of Windows. Under certain circumstances involving Diffie-Hellman key exchange, SChannel is unable to correctly handle input from the server. This bug has already been fixed in recent patches for Windows 10 and Windows Server 2016, but they are not yet available for AppVeyor. Manually pamper over that issue by disabling all ciphersuites using DHE via the registry. While this disables more ciphers than necessary, we really don't care for that at all but just want to avoid build failures due to that bug. See [1], [2] or [3] for additional information. 1: https://github.com/aws/aws-sdk-cpp/issues/671 2: https://github.com/dotnet/corefx/issues/7812 3: https://support.microsoft.com/en-us/help/2992611/ms14-066-vulnerability-in-schannel-could-allow-remote-code-execution-n
54a1bf05	2017-06-07T13:06:53	tests: online::clone: inline creds-test with nonexistent URL Right now, we test our credential callback code twice, once via SSH on localhost and once via a non-existent GitHub repository. While the first URL makes sense to be configurable, it does not make sense to hard-code the non-existing repository, which requires us to call tests multiple times. Instead, we can just inline the URL into another set of tests.
fea60920	2017-06-07T12:48:48	tests: online::clone: construct credential-URL from environment We support two types of passing credentials to the proxy, either via the URL or explicitly by specifying user and password. We test these types by modifying the proxy URL and executing the tests twice, which is in fact unnecessary and requires us to maintain the list of environment variables and test executions across multiple CI infrastructures. To fix the situation, we can just always pass the host, port, user and password to the tests. The tests can then assemble the complete URL either with or without included credentials, allowing us to test both cases in-process.
0b98a66b	2017-11-06T11:16:02	appveyor: build examples By default, CMake will not build our examples directory. As we do not instruct either the MinGW or MSVC builds on AppVeyor to enable building these examples, we cannot verify that those examples at least build on Windows systems. Fix that by passing `-DBUILD_EXAMPLES=ON` to AppVeyor's CMake invocation.
03a95bc5	2017-09-15T11:32:46	appveyor: add jobs to also build on Visual Studio 2015 In order to cover a wider range of build environments, add two more jobs which build and test libgit2 on Visual Studio 14 2015.
e1076dbf	2017-09-15T10:01:36	appveyor: explicitly specify build images AppVeyor currently does provide three standard build worker images with VS2013, VS2015 and VS2017. Right now, we are using the implicitly, which is the VS2015 one. We want to be more explicit about this, so that we can easily switch build images based on the job. So starting from this commit, we explicitly set the `APPVEYOR_BUILD_WORKER_IMAGE` variable per job, which enables us to choose different images. To be able to test a wider range of build configurations, this commit also switches the jobs for VC2010 over to use the older, VS2013 based images. As the next commit will introduce two new jobs for building with VS2015, we have then covered both build environments. Also, let us be a bit more explicit regarding the CMake generator. Instead of only saying "Visual Studio 10", use the more descriptive value "Visual Studio 10 2010" to at least avoid some confusion surrounding the versioning scheme of Visual Studio.
c3abb1d2	2017-02-24T17:38:42	appveyor: always build the 'appveyor' branch The 'appveyor' branch is useful for testing AppVeyor builds.
247665ed	2016-05-25T12:10:44	Use AppVeyor's Start-FileDownload cmdlet Start-FileDownload maintains current directory context and allows specifying a request timeout, see [1]. [1] https://www.appveyor.com/docs/how-to/download-file#start-filedownload-cmdlet
2638df77	2016-04-19T23:05:16	CI: download the proxy jar also on mingw We were downloading the jar from within an block which only runs for MSVC. Move the download to the start of the test so it gets downloaded for both.
b8353236	2016-04-19T10:50:30	CI: run proxy tests with ctest Running clar directly on appveyor makes it think the command returned failure, so it stops the tests. Running it via ctest lets it go through.
db01724f	2016-03-14T13:42:10	CI: start the proxy before the build so it's ready It takes a bit for the propxy to get ready to accept connections, so start it before the build so we can be reasonably sure that it's going to be ready in time.
22e6aa0d	2015-09-23T04:39:05	proxy: don't require the trailing slash on WinHTTP The path is not something that you use for proxies, so make use of the new optionality of the path when extracting URL parts.
b117721d	2015-07-29T21:23:56	proxy: use poxy to test our Windows proxy support
fa31ee68	2016-03-14T15:00:59	Merge pull request #3671 from libgit2/cmn/remove-mingw32 Remove CI support for mingw32
b1093e62	2016-03-09T19:01:33	Remove CI support for mingw32 The tests have never run successfully and we do have successful builds of mingw-w64, so remove these CI builds which do not add value.
113e1634	2016-03-09T19:20:38	appveyor: stop if the first test fails
ba9bb664	2016-03-03T19:21:07	tests: create a ctest target for cred_callback
25205737	2016-03-03T10:08:00	test: make sure we retry the auth callback on all platforms We were missing this test on Windows, which meant we didn't notice that we never fixed the single authentication attempt it tries, nor its wrong return code. Enable this for the unix platforms as well over HTTP. We previously were doing it locally but disabled it on OS X due to issues with its sshd not accepting password authentication.
2a306776	2015-05-22T14:02:44	build maint branches on appveyor equivalent of ca183d27366ba75597a9806b746e42a074df7795
d06c589f	2015-04-10T06:15:06	Add MSVC CRTDBG memory leak reporting.
9a08b319	2015-03-10T16:08:44	Revert "add fast-fail feature for pending builds in PR's" This reverts commit 8008ab6a4158416d095212c9782fa1622ef994a5.
2326ea68	2015-03-05T16:14:17	Allow failures on mingw for now
4c88fd7c	2015-03-04T11:31:24	Add MinGW-w64 to matrix cache mingw-w64 downloads quiet curl and 7zip run appveyor steps in cmd for mingw
8008ab6a	2015-03-03T17:03:07	add fast-fail feature for pending builds in PR's
ac5fad27	2015-03-03T10:53:26	add mingw to appveyor matrix use MSYS makefiles generator add bash script for running mingw on appveyor add --login and fix run paths use msys style path to appveyor-mingw.sh add mingw path to /etc/fstab
feb0e022	2015-02-19T12:14:06	tests: separate INVASIVE filesystem tests Introduce GITTEST_INVASIVE_FS_STRUCTURE for things that are invasive to your filesystem structure (like creating folders at your filesystem root) and GITTEST_INVASIVE_FS_SIZE for things that write lots of data.
e07c1e1a	2015-02-12T00:40:12	Merge pull request #2880 from ethomson/mkdir_root Ensure we can make a repo at the root of the filesystem
554063a5	2015-02-06T23:12:58	Speed up AppVeyor builds. AppVeyor build machines come with Python 2.7 and CMake 2.8 pre-installed and in the PATH.
2f4ee000	2015-02-05T11:55:00	appveyor: include the invasive filesystem tests
f4e3a6ab	2015-01-31T22:15:10	AppVeyor: Prettify build script
1d67e8fd	2015-01-16T21:28:25	Windows CI: use 32 and 64 bit for AppVeyor builds Add 64 bit and always build with default calling conventions, to avoid trying to build with stdcall on amd64.
388ca7e7	2015-01-06T15:16:25	Add appveyor yaml

ce798b25

2018-07-04T10:56:56

tests: simplify cmake test configuration 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.

3a72b0e2

2018-04-03T12:31:35

appveyor: fix typo in registry key to disable DHE Commit 723e1e976 (appveyor: disable DHE to avoid spurious failures, 2018-03-29) added a workaround to fix spurious test failures due to a bug in Windows' SChannel implementation. The workaround only worked by accident, though, as the registry key was in fact mistyped. Fix the typo.

723e1e97

2018-03-29T13:35:27

appveyor: disable DHE to avoid spurious failures Our CI builds have intermittent failures in our online tests, e.g. with the message "A provided buffer was too small". This is not a programming error in libgit2 but rather an error in the SChannel component of Windows. Under certain circumstances involving Diffie-Hellman key exchange, SChannel is unable to correctly handle input from the server. This bug has already been fixed in recent patches for Windows 10 and Windows Server 2016, but they are not yet available for AppVeyor. Manually pamper over that issue by disabling all ciphersuites using DHE via the registry. While this disables more ciphers than necessary, we really don't care for that at all but just want to avoid build failures due to that bug. See [1], [2] or [3] for additional information. 1: https://github.com/aws/aws-sdk-cpp/issues/671 2: https://github.com/dotnet/corefx/issues/7812 3: https://support.microsoft.com/en-us/help/2992611/ms14-066-vulnerability-in-schannel-could-allow-remote-code-execution-n

54a1bf05

2017-06-07T13:06:53

tests: online::clone: inline creds-test with nonexistent URL Right now, we test our credential callback code twice, once via SSH on localhost and once via a non-existent GitHub repository. While the first URL makes sense to be configurable, it does not make sense to hard-code the non-existing repository, which requires us to call tests multiple times. Instead, we can just inline the URL into another set of tests.

fea60920

2017-06-07T12:48:48

tests: online::clone: construct credential-URL from environment We support two types of passing credentials to the proxy, either via the URL or explicitly by specifying user and password. We test these types by modifying the proxy URL and executing the tests twice, which is in fact unnecessary and requires us to maintain the list of environment variables and test executions across multiple CI infrastructures. To fix the situation, we can just always pass the host, port, user and password to the tests. The tests can then assemble the complete URL either with or without included credentials, allowing us to test both cases in-process.

0b98a66b

2017-11-06T11:16:02

appveyor: build examples By default, CMake will not build our examples directory. As we do not instruct either the MinGW or MSVC builds on AppVeyor to enable building these examples, we cannot verify that those examples at least build on Windows systems. Fix that by passing `-DBUILD_EXAMPLES=ON` to AppVeyor's CMake invocation.

03a95bc5

2017-09-15T11:32:46

appveyor: add jobs to also build on Visual Studio 2015 In order to cover a wider range of build environments, add two more jobs which build and test libgit2 on Visual Studio 14 2015.

e1076dbf

2017-09-15T10:01:36

appveyor: explicitly specify build images AppVeyor currently does provide three standard build worker images with VS2013, VS2015 and VS2017. Right now, we are using the implicitly, which is the VS2015 one. We want to be more explicit about this, so that we can easily switch build images based on the job. So starting from this commit, we explicitly set the `APPVEYOR_BUILD_WORKER_IMAGE` variable per job, which enables us to choose different images. To be able to test a wider range of build configurations, this commit also switches the jobs for VC2010 over to use the older, VS2013 based images. As the next commit will introduce two new jobs for building with VS2015, we have then covered both build environments. Also, let us be a bit more explicit regarding the CMake generator. Instead of only saying "Visual Studio 10", use the more descriptive value "Visual Studio 10 2010" to at least avoid some confusion surrounding the versioning scheme of Visual Studio.

c3abb1d2

2017-02-24T17:38:42

appveyor: always build the 'appveyor' branch The 'appveyor' branch is useful for testing AppVeyor builds.

247665ed

2016-05-25T12:10:44

Use AppVeyor's Start-FileDownload cmdlet Start-FileDownload maintains current directory context and allows specifying a request timeout, see [1]. [1] https://www.appveyor.com/docs/how-to/download-file#start-filedownload-cmdlet

2638df77

2016-04-19T23:05:16

CI: download the proxy jar also on mingw We were downloading the jar from within an block which only runs for MSVC. Move the download to the start of the test so it gets downloaded for both.

b8353236

2016-04-19T10:50:30

CI: run proxy tests with ctest Running clar directly on appveyor makes it think the command returned failure, so it stops the tests. Running it via ctest lets it go through.

db01724f

2016-03-14T13:42:10

CI: start the proxy before the build so it's ready It takes a bit for the propxy to get ready to accept connections, so start it before the build so we can be reasonably sure that it's going to be ready in time.

22e6aa0d

2015-09-23T04:39:05

proxy: don't require the trailing slash on WinHTTP The path is not something that you use for proxies, so make use of the new optionality of the path when extracting URL parts.

b117721d

2015-07-29T21:23:56

proxy: use poxy to test our Windows proxy support

fa31ee68

2016-03-14T15:00:59

Merge pull request #3671 from libgit2/cmn/remove-mingw32 Remove CI support for mingw32

b1093e62

2016-03-09T19:01:33

Remove CI support for mingw32 The tests have never run successfully and we do have successful builds of mingw-w64, so remove these CI builds which do not add value.

113e1634

2016-03-09T19:20:38

appveyor: stop if the first test fails

ba9bb664

2016-03-03T19:21:07

tests: create a ctest target for cred_callback

25205737

2016-03-03T10:08:00

test: make sure we retry the auth callback on all platforms We were missing this test on Windows, which meant we didn't notice that we never fixed the single authentication attempt it tries, nor its wrong return code. Enable this for the unix platforms as well over HTTP. We previously were doing it locally but disabled it on OS X due to issues with its sshd not accepting password authentication.

2a306776

2015-05-22T14:02:44

build maint branches on appveyor equivalent of ca183d27366ba75597a9806b746e42a074df7795

d06c589f

2015-04-10T06:15:06

Add MSVC CRTDBG memory leak reporting.

9a08b319

2015-03-10T16:08:44

Revert "add fast-fail feature for pending builds in PR's" This reverts commit 8008ab6a4158416d095212c9782fa1622ef994a5.

2326ea68

2015-03-05T16:14:17

Allow failures on mingw for now

4c88fd7c

2015-03-04T11:31:24

Add MinGW-w64 to matrix cache mingw-w64 downloads quiet curl and 7zip run appveyor steps in cmd for mingw

8008ab6a

2015-03-03T17:03:07

add fast-fail feature for pending builds in PR's

ac5fad27

2015-03-03T10:53:26

add mingw to appveyor matrix use MSYS makefiles generator add bash script for running mingw on appveyor add --login and fix run paths use msys style path to appveyor-mingw.sh add mingw path to /etc/fstab

feb0e022

2015-02-19T12:14:06

tests: separate INVASIVE filesystem tests Introduce GITTEST_INVASIVE_FS_STRUCTURE for things that are invasive to your filesystem structure (like creating folders at your filesystem root) and GITTEST_INVASIVE_FS_SIZE for things that write lots of data.

e07c1e1a

2015-02-12T00:40:12

Merge pull request #2880 from ethomson/mkdir_root Ensure we can make a repo at the root of the filesystem

554063a5

2015-02-06T23:12:58

Speed up AppVeyor builds. AppVeyor build machines come with Python 2.7 and CMake 2.8 pre-installed and in the PATH.

2f4ee000

2015-02-05T11:55:00

appveyor: include the invasive filesystem tests

f4e3a6ab

2015-01-31T22:15:10

AppVeyor: Prettify build script

1d67e8fd

2015-01-16T21:28:25

Windows CI: use 32 and 64 bit for AppVeyor builds Add 64 bit and always build with default calling conventions, to avoid trying to build with stdcall on amd64.

388ca7e7

2015-01-06T15:16:25

Add appveyor yaml

thodg/libgit2/appveyor.yml

appveyor.yml

Log