inconsistent timestamp intervals in prime.log
 

Not sure whether this is an issue, but I noticed that the timestamp intervals are sometimes inconsistent when Prime95 updates the log file. At first I thought the interval was 300 seconds, like in the case of the results file. However, sometimes Prime95 writes a new timestamp even when the previous entry was added just seconds earlier:

[QUOTE][Fri Jun 21 19:22:37 2019 - ver 29.8]
Exchanging program options with server
[Fri Jun 21 19:22:54 2019 - ver 29.8]
Exchanging program options with server[/QUOTE]

I've also seen Prime95 add entries under the same timestamp even though the previous one was written more than five minutes ago:

[QUOTE][Fri Dec 6 18:18:35 2019 - ver 29.8]
Updating computer information on the server
Updating computer information on the server
Sending expected completion date for M92524109: Dec 8 2019
Sending expected completion date for M92771191: Dec 14 2019
Sending expected completion date for M92524177: Dec 8 2019
Sending expected completion date for M92771219: Dec 14 2019
Sending result to server: UID: ixfd64/mbpro-2, M92524109 completed P-1, B1=710000, B2=13312500, E=6, Wh10: 59430D1F, AID: F6AEE7A97A25FD3B7B3BADABA1189C3F

PrimeNet success code with additional info:
CPU credit is 7.3354 GHz-days.
Sending result to server: UID: ixfd64/mbpro-2, M92524177 completed P-1, B1=710000, B2=13312500, E=6, Wh10: 597E0D1F, AID: A0A22B1B2060B898C8B20BBA18C3EA15

PrimeNet success code with additional info:
CPU credit is 7.3354 GHz-days.[/QUOTE]

In this particular case, the results were reported over 30 minutes apart:

[QUOTE][Sat Dec 7 00:10:46 2019]
UID: ixfd64/mbpro-2, M92524177 completed P-1, B1=710000, B2=13312500, E=6, Wh10: 597E0D1F, AID: A0A22B1B2060B898C8B20BBA18C3EA15
[/QUOTE]

Is there a reason for this?

I noticed that Prime95 version 30.3 behaves the same way on Windows. So this is probably intentional.