| commit | ff8dbafd022e65ac5e932c88e8691ac8dac1602c | |
| 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> | |
| Tue, 5 Jun 2012 18:44:22 +0000 (5 13:44 -0500) | ||
| tree | 1158de2f1197b9bd9a0c7919c24cbb1f0e0c4b39 | treesnapshot (tar.gz zip) |
| parent | 9f5fe626ddb6ef5fbe6feedd7eb621ac838f0527 | 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 |