tree e7a1fdb5d7550d32ce9de1ee299411f95730cd58
parent c3e8d153316035a0c24d8383be1cb2390752ab82
author Saša Živkov <sasa.zivkov@sap.com> 1557908014 +0200
committer David Pursehouse <dpursehouse@collab.net> 1562211529 +0900

When rescheduling due to in-flight push log also the in-flight task ID

When a push operation was rescheduled due to an in-flight push we logged
a line like:

   [79bda07a] Rescheduling replication to https://host/foo.git to avoid collision with an in-flight push.

This log was already useful but it didn't tell us which push task was
actually in-flight.

Add the ID of the in-flight push task to the log:

   [79bda07a] Rescheduling replication to https://host/foo.git to avoid collision with the in-flight push [80ceb18b].

This information is especially useful when a task gets repeatedly
rescheduled and we need to identify the root cause of that.

(cherry picked from commit f585eba0d21be222404b871bfe7a2b11e578eb14)
Change-Id: I7866f964cab1e4f479b0d7d62ae4aac3019fab4b