delta/libgit2.git/.travis.yml, branch cmn/https-cap-no-hardcode github.com: libgit2/libgit2.git travis: do not allow valgrind failures 2016-10-31T15:01:10+00:00 Patrick Steinhardt ps@pks.im 2016-10-28T12:57:54+00:00 0334bf4b24401c73cb9c9e2211bc4858e61b5934 Our valgrind jobs haven't been failing for several builds by now. This indicates that our tests are sufficiently stable when running under valgrind. As such, any failures reported by valgrind become interesting to us and shouldn't be ignored when causing a build to fail. Remove the valgrind job from the list of allowed failures. 
Our valgrind jobs haven't been failing for several builds by now.
This indicates that our tests are sufficiently stable when
running under valgrind. As such, any failures reported by
valgrind become interesting to us and shouldn't be ignored when
causing a build to fail.

Remove the valgrind job from the list of allowed failures.
Remove CI support for mingw32 2016-03-14T10:05:58+00:00 Carlos Martín Nieto cmn@dwim.me 2016-03-09T18:01:33+00:00 b1093e62d521b2625f1651a3c2083a0c3e92ffad 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. 
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.
travis ci: enable debug pool for valgrind builds 2016-02-28T16:34:36+00:00 Edward Thomson ethomson@github.com 2016-02-28T16:34:36+00:00 da0335604410f57982f973a1f05a8e2c719eb137 






Always install valgrind via the apt addon.
2015-06-27T12:54:19+00:00

Arthur Schreiber
schreiber.arthur@googlemail.com

2015-06-27T12:54:19+00:00

b48dfe0bbe73c1b17ff645fdbe3dcd321b2b5a7b












Fast builds?
2015-06-26T15:58:45+00:00

Arthur Schreiber
arthur.schreiber@hp.com

2015-06-26T15:58:45+00:00

76d7c359afe464930585734322ba8ea468a35bfc












travis: build maint branches
2015-05-22T15:44:28+00:00

Carlos Martín Nieto
cmn@dwim.me

2015-05-22T15:44:28+00:00

ca183d27366ba75597a9806b746e42a074df7795












Win32: Enable WinHTTP for MinGW
2015-03-16T19:59:55+00:00

Philip Kelley
phkelley@hotmail.com

2014-06-09T15:43:25+00:00

8f426d7dd26856150950d080fb821044bb2ea811












tests: separate INVASIVE filesystem tests
2015-02-19T17:14:06+00:00

Edward Thomson
ethomson@microsoft.com

2015-02-19T17:14:06+00:00

feb0e022867552c039c02fe39db7b7c3d63ae327

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.





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.







Travis: do non-threadsafe builds
2014-11-22T17:46:17+00:00

Carlos Martín Nieto
cmn@dwim.me

2014-11-22T17:46:17+00:00

1dbb74baf2a2d0a4e2b7f487f45c8d3875a106ae

When flipping the default to threadsafe, we never made sure that the
tests were building non-threadsafe variants. Specify which thead-safety
we want for each.





When flipping the default to threadsafe, we never made sure that the
tests were building non-threadsafe variants. Specify which thead-safety
we want for each.







Travis: move the valgrind run to allowed_failures
2014-11-22T17:42:00+00:00

Carlos Martín Nieto
cmn@dwim.me

2014-11-22T17:42:00+00:00

60f3e876c5a75ff89d021fbdec6426ad4a7a2379

We don't need to know the result of the travis run before determining
whether we want to consider the merge as successful.





We don't need to know the result of the travis run before determining
whether we want to consider the merge as successful.