| commit | b27224016286e594c56e32c4998b823c7e4bbff9 | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Tue, 29 May 2012 00:58:50 +0000 (28 19:58 -0500) | ||
| committer | Pat Thoyts <patthoyts@users.sourceforge.net> | |
| Tue, 19 Jun 2012 22:45:09 +0000 (19 23:45 +0100) | ||
| tree | 88fa5dc749db6bceb2ab71965fb2fc8611bfca54 | treesnapshot (tar.gz zip) |
| parent | 64fa56d88f6242ebb3b9e53419be9573c9b211f2 | commitdiff |
Work around a problem identified by BuildHive
Apparently the signal handling is not quite correct in the fsckobject
handling (most likely we rely on a side effect that lets us still output
some message after receiving a signal 13 but in the BuildHive setup this
fails intermittently).
As a consequence, the push in t5504 does fail as expected, but fails to
output anything (unexpected). Since this is good enough for now, let's
handle an empty output as success, too.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Apparently the signal handling is not quite correct in the fsckobject
handling (most likely we rely on a side effect that lets us still output
some message after receiving a signal 13 but in the BuildHive setup this
fails intermittently).
As a consequence, the push in t5504 does fail as expected, but fails to
output anything (unexpected). Since this is good enough for now, let's
handle an empty output as success, too.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
| t/t5504-fetch-receive-strict.sh | diffblobblamehistory |