| commit | 0ec21197db673a28c7d9e9f6346271f3d28e9343 | |
| 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> | |
| Wed, 16 Jan 2013 09:52:54 +0000 (16 09:52 +0000) | ||
| tree | ba14ba8607b5674dd504dbf1cc2972b98aed1506 | treesnapshot (tar.gz zip) |
| parent | 28a935a3526c209f0cb35f835e37d34b7f071928 | 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 |