I have yet to see a beta unit successfully complete:
<core_client_version>8.0.2</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)</message>
<stderr_txt>
Commandline = ../../projects/www.worldcommunitygrid.org/wcgrid_beta30_map_7.04_x86_64-pc-linux-gnu -SettingsFile BETA30_9800010_0613.txt -DatabaseFile dataset-curatedArthritis_LesionNonL_PsO_PsA_AS_v1.0.txt
Settings File
DateOfDesign = 20250425
Designer = Krembil/cubes
WorkOrderID = BETA30_9800010_0613
.
.
.
terminate called after throwing an instance of 'boost::archive::archive_exception'
what(): input stream error
SIGABRT: abort called

I had two of these, one ran for 3.54 hours and the other one ran for 2.04 hours on the same machine.

Cheers

Observations:
24 Validated Tasks
Lots that are extremely slow or stuck. Here is a breakdown, maybe you all see different results:

9800000- None have completed or validated
9800005- One validation (Linux) but it took a LONG time to complete
9800008- Best generation, seems to process well in Linux AND Windows
9800009- Some validations in Linux
9800010- No completed tasks, seem to hang
9800011- No completed tasks, seem to hang
9800013- None have completed or validated
9800014- None have completed or validated
9800015- None have completed or validated
9800016- None have completed or validated
9800017- None have completed or validated
9800018- None have completed or validated
9800019- None have completed or validated
9800016- None have completed or validated
9800021- Validations in Linux
9800023- No completed tasks, seem to hang
9800025- None have completed or validated
9800026- None have completed or validated
9800028- None have completed or validated
9800029- None have completed or validated

I noticed that one of the tasks ( BETA30_9800015_0249 ) that was stuck at 0.5% after more than 20 hours of computing had the following file in slots:
wcg_checkpoint_00.ckp
0.000000 20000.000000 0.000000 1 0
Also, there is a line in stderr.txt:
NReps = 10
I assume, that was the first try and 9 to go. So, probably they are not stuck, they are just slow.
(i7-5775C, linux)

There is a file wcg_rng.state with some numbers:
4178955793 43298860 3398312549 2866235683 1464173292 3342755232...
etc

Until I see some comment from the tech team, I'm going to abort them. 340 so far.

The entire original content of this message has been rendered obsolete by the latest Jurisica Labs Operational Status update (which wasn't there when I started, the core BOINC services still being down at the time...)

Instead, I'll note that if WCG set up a thread in this forum specifically for reporting on our experiences it would:

• give a focal point for our feedback, rather than the current case where there's relevant comment in three or four different threads;
  
• offer an opportunity for WCG to let us know when we might as well abort tasks in a specific batch;
  
• allow brief notes from WCG regarding things such as new data sets.
  

Just a thought...

Cheers - Al.