| commit | d2699ac5ef1669c18aa791bb8a4d6d3791d4318c | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Tue, 29 May 2012 00:58:50 +0000 (28 19:58 -0500) | ||
| committer | Stepan Kasal <kasal@ucw.cz> | |
| Wed, 16 Apr 2014 14:32:50 +0000 (16 16:32 +0200) | ||
| tree | ae548596b19d7942648da8abf4ed0905b7d4b88a | treesnapshot (tar.gz zip) |
| parent | 13b10e0a7c84ca8e6655d40d4baee570ce6358fe | 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 |