Affects Version/s: None
Fix Version/s: 1.1-rc-1
I'm seeing this on windows when the indexer is on.
It manifests as java.io.IOException: Unable to delete file/directory, and then a subsequent clean will succeed.
We could cater for this by noting that a particular operation failed, and then retrying it again at the end or after some time.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Fix Version/s||1.1-rc-1 [ 10360 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
|Summary||Cleaning should be more robust (e.g. to deal with OS indexers that quickly lock/unlock files)||Cleaning should be more robust on Windows|
|Assignee||Luke Daley [ ldaley ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Workflow||jira with pivotal tracker [ 15595 ]||jira with pivotal tracker (no resolved, only closed) [ 17668 ]|
|Status||Closed [ 6 ]||Resolved [ 5 ]|
|Workflow||jira with pivotal tracker (no resolved, only closed) [ 17668 ]||Copy of jira with pivotal tracker (no closed, only resolved) [ 20303 ]|