rick olson
b0f3d49e71
use a channel to ensure STDOUT receives all test results before exiting
2017-11-17 08:45:12 -07:00
Sebastian Schuberth
296c95ed71
Fix determining the path to bash on Windows
...
Windows' "where" tool can potentially return multiple findings, one per
line. This is especially the case with the Windows 10 Ubuntu Bash
installed (which is located at "C:\Windows\System32\bash.exe").
Fix determining the path by only returning the first line / match if the
output is non-empty.
2016-09-28 21:30:05 +02:00
risk danger olson
3a3f0e14f5
set default test maxprocs back to 4
2016-07-15 15:07:56 -06:00
risk danger olson
519b5f69b9
print the maxprocs message right before kicking off the test workers
2016-07-15 15:05:25 -06:00
risk danger olson
99af66b485
set default test procs on mac to 1
2016-07-15 14:55:48 -06:00
risk danger olson
c0a2b8988b
unreachable
2016-07-15 11:45:50 -06:00
risk danger olson
d3c9c72616
teach script/integration.go about GIT_LFS_TEST_MAXPROCS
2016-07-15 10:33:42 -06:00
risk danger olson
caee1d5986
send output before killing
2016-04-11 10:29:20 -06:00
risk danger olson
676611deec
add timeouts to script/integration, with partial output
2016-04-11 10:16:46 -06:00
Steve Streeting
c8a6320f95
Fix running integration tests on Windows
...
Was failing because absolute path to bash was expressed as MinGW path
which cannot be executed from Go directly (only from Git bash!)
2016-03-14 15:04:55 +00:00
risk danger olson
b89d912bcf
update integration script to look for bash
2015-10-27 07:11:29 -06:00
risk danger olson
589ab9bd99
backslashes
2015-10-27 07:04:54 -06:00
risk danger olson
626190f7c5
add debugging
2015-10-27 07:03:18 -06:00
Steve Streeting
f12d409a01
Make sure we don't accidentally run *.sh.orig (merge remnants) in test
2015-10-27 08:47:09 +00:00
risk danger olson
47d167feea
return exit code 1 if any of the tests fail
2015-10-26 16:30:49 -06:00
risk danger olson
807bb3e1b2
rewrite test runner in go to reduce output race conditions
2015-10-26 16:25:31 -06:00
