817d09bdc8
* Update plugins/replication from branch 'stable-3.2'
to cc72dc5cb3e4198ebd4f487a3fcc04846e1ceb43
- Merge branch 'stable-3.1' into stable-3.2
* stable-3.1:
Call retryDone() when giving up after lock failures
Fix issue with task cleanup after retry
Change-Id: I6dbeaa0d21545a1903bdb11c5de5d9e8f72079c5
- Merge branch 'stable-3.0' into stable-3.1
* stable-3.0:
Call retryDone() when giving up after lock failures
Fix issue with task cleanup after retry
Change-Id: Id9ce63cd6112b3c8b16f9daafe3a8a982521baa9
- Merge branch 'stable-2.16' into stable-3.0
* stable-2.16:
Call retryDone() when giving up after lock failures
Fix issue with task cleanup after retry
Change-Id: Id987043c8a26bd3f69fb4bd5b84591ae20cb83ba
- Call retryDone() when giving up after lock failures
Previously when giving up after retrying due to too many lock failures,
a 'replication start --wait' command would wait indefinitely if it was
waiting on the push that gave up. Fix this by calling retryDone() after
giving up which will trigger the ReplicationStatus to reflect a failure
allowing the waiting to complete.
Change-Id: I0debade83612eb7ce51bab0191ab99464a6e7cd3
- Fix issue with task cleanup after retry
Destination.notifyFinished method calls finish on
ReplicationTasksStorage.Task objects which are not scheduled for retry.
The issue is that for rescheduled tasks PushOne.isRetrying
will always returns true even if task is already replicated.
That creates a situation where tasks scheduled for retry are
never cleaned up.
Bug: Issue 12754
Change-Id: I4b10c2752da6aa7444f57c3ce4ab70eb00c3f14e
|
||
|---|---|---|
| .. | ||
| codemirror-editor@e211fb1bd2 | ||
| commit-message-length-validator@556e427fd7 | ||
| delete-project@76f5b25733 | ||
| download-commands@e26ed31aaf | ||
| gitiles@b8ea789876 | ||
| hooks@7ed555fe88 | ||
| plugin-manager@783f5c65c7 | ||
| replication@cc72dc5cb3 | ||
| reviewnotes@e952b920ec | ||
| singleusergroup@b594c7f7d6 | ||
| webhooks@9fc9c2d4e6 | ||
| BUILD | ||
| external_plugin_deps.bzl | ||