This pair of workunit results seems strange. The _1 CPU time of 0.45 hour attracted my attention, as it was so much faster than my _0's 2.2 hours. What a fast machine, I thought.

ZIKA_ 000000012_ x4e78_ HCV_ 2aJFH1_ NS5Bpol_ DelRNA_ 0210_ 1-- Microsoft Windows 7 Professional x64 Edition, Service Pack 1, (06.01.7601.00) 705 Valid 18/05/16 15:43:19 19/05/16 14:21:43 0.45 15.6 / 50.5
ZIKA_ 000000012_ x4e78_ HCV_ 2aJFH1_ NS5Bpol_ DelRNA_ 0210_ 0-- Microsoft Windows 10 Professional x64 Edition, (10.00.10586.00) 705 Valid 18/05/16 15:42:36 19/05/16 19:59:03 2.20 85.5 / 50.5

However, a glance at the Result Logs showed that my machine was completing each of the 23 tasks more quickly. There were also several instances of these errors in _1:

10:13:54 (5808): Can't acquire lockfile (32) - exiting
10:13:54 (5808): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.
(0x20)
10:15:17 (4376): Can't acquire lockfile (32) - waiting 35s
10:15:52 (4376): Can't acquire lockfile (32) - exiting
10:15:52 (4376): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.
(0x20)

Then at the end in _1, there's this; it looks as if the workunit was restarting after it had finished:

[15:49:54] Finished task #22 cpu time used 634.565268
15:49:54 (3184): called boinc_finish(0)
[16:15:13] Number of tasks = 23
16:15:13 (2600): called boinc_finish(0)

</stderr_txt>

Finally, _1 then declares the unnaturally short 0.45 hours, but the overall result of the pair is validated. I just wondered if this combination was an acceptable validator outcome?