Thank you for the confirmation.

Mike

ARP1_0034392_089 has completely crashed out. Eight systems, eight errors.

Thank you spRocket. I thought it would.

Mike

A quick update on the stuck workunits.

There are 47 stuck workunits left - the rest have been set in motion.

Of these:

• 3 might have to be re-run from the beginning
  
• 3 cannot be processed even with changing the more granular step_size of 24
  

those 6 will be examined by Delft before we can get them running again.

Of the remaining 41, we are re-running them on our servers before we put them back on the grid. This is a slightly slow process but it allows us to be sure that we understand the issue and that they are running properly before we send them out again. Some have to be re-run for multiple generations and as a result we have only been able to put 4-5 back into circulation each day. With the help of Delft, we have a way to detect the issue in the validator so we will identify this issue in the first generation it occurs in from now on so we shouldn't get these stuck jobs again (we will still have to periodically re-run the jobs with a smaller step size).

I hope to have the remaining 41 running again within the next 7-10 days.

Another undiscovered triplet, 32-bit, time_step=36:
workunit 130444485

ARP1_0004211_085_0  Linux Fedora  Valid    2022-01-25T15:27:12  2022-01-26T07:03:02   14.12/14.42    576.9/609.0 
ARP1_0004211_085_1  Linux Ubuntu  Valid    2022-01-25T15:26:24  2022-01-26T05:56:14   13.25/13.29    641.1/609.0 
ARP1_0004211_085_2  Linux Debian  InProgr  2022-01-25T15:33:38  2022-01-30T03:33:38    0.00/0.00       0.0/0.0   

Cheers,
Adri