| commit | 0639601635751cff1193899713f1bb58d19398f5 | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Tue, 29 May 2012 00:58:50 +0000 (28 19:58 -0500) | ||
| committer | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Fri, 20 Dec 2013 00:24:44 +0000 (19 18:24 -0600) | ||
| tree | 61e669fd9aa6248fb149f34fd3a77f34c4fc1259 | treesnapshot (tar.gz zip) |
| parent | 2b023e567856c377102d94dbdfb8f31fee64ee87 | 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 |