07-09-2018, 08:07 PM
Thank you for your response.
Indeed the status is exhausted even though "Progress" and "Restore.Point" is below 100.00%. Up to now I did not log the return code thus there is nothing to tell. I modified it and give it another try, but as a result of the unpredictability I do not know when I can tell it.
Dunno if this helps:
I looked up some logs and in all that cases the first error was written on the same line as "[s]tatus" and it was written to occur in "clWaitForEvents", then another clWaitForEvents and four times "clEnqueueReadBuffer", before the "Status.[...]: Exhausted" line.
Indeed the status is exhausted even though "Progress" and "Restore.Point" is below 100.00%. Up to now I did not log the return code thus there is nothing to tell. I modified it and give it another try, but as a result of the unpredictability I do not know when I can tell it.
Dunno if this helps:
I looked up some logs and in all that cases the first error was written on the same line as "[s]tatus" and it was written to occur in "clWaitForEvents", then another clWaitForEvents and four times "clEnqueueReadBuffer", before the "Status.[...]: Exhausted" line.