author | Brian Gernhardt <brian@gernhardtsoftware.com> | |
Sat, 6 Feb 2010 14:50:03 +0000 (09:50 -0500) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Sat, 6 Feb 2010 18:33:07 +0000 (10:33 -0800) | ||
commit | ab35469de0d2d2ba4be58fd0231687ddc9cc3cdc | |
tree | 2ffc9026aaa8e958bb66539f40b17fb1972a10b2 | tree | snapshot |
parent | 6d0d465e20b8c11924bc4e75563324771d0e0d63 | commit | diff |
t9501: Re-fix max load test
Revert the previous attempt to skip this test on platforms where we
currently cannot determine the system load. We want to make sure that
the max-load-limit codepath produces results cleanly, when gitweb is
updated and becomes capable of reading the load average by some other
method.
The code to check for load returns 0 if it doesn't know how to find
load. It also checks to see if the current load is higher than the
max load. So to force the script to quit early by setting the maxload
variable negative which should work for systems where we can detect
load (which should be a positive number) and systems where we can't
(where detected load is 0)
Signed-off-by: Brian Gernhardt <brian@gernhardtsoftware.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Revert the previous attempt to skip this test on platforms where we
currently cannot determine the system load. We want to make sure that
the max-load-limit codepath produces results cleanly, when gitweb is
updated and becomes capable of reading the load average by some other
method.
The code to check for load returns 0 if it doesn't know how to find
load. It also checks to see if the current load is higher than the
max load. So to force the script to quit early by setting the maxload
variable negative which should work for systems where we can detect
load (which should be a positive number) and systems where we can't
(where detected load is 0)
Signed-off-by: Brian Gernhardt <brian@gernhardtsoftware.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t9501-gitweb-standalone-http-status.sh | diff | blob | history |