compute error with:

1390773
1390766

both with message:

ERROR: ERROR: FragmentIO: could not open file aa9mer.1_3.gz
ERROR:: Exit from: ....srccorefragmentFragmentIO.cc line: 245
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

looks a similar fault to some already posted

Also had the same/similar error on Result 1391999
Result 1394906

ERROR: ERROR: FragmentIO: could not open file aa9mer.1_3.gz
ERROR:: Exit from: src/core/fragment/FragmentIO.cc line: 245
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

---

Seven days and no bad tasks? I know we don't get that many total ... but ... isn't about time to promote 1.58 to operational while we chase these last buglets?

I know 1.54 is decent, but, 1.58 is marginally better in stability ...

What about it guys?

I agree. On the 10th of March I asked when it was going over to the main project, I'm yet to get a answer

I agree. On the 10th of March I asked when it was going over to the main project, I'm yet to get a answer

They haven't said anything about the bad tasks in like forever also ...

This task seemed to have hung, tried graphics on it and got a black window. The window would not close so got a GPF for my troubles. The task seems to have "hung" after that and went into high priority mode and no advance on the percentage complete so I shot it.

1utg__BOINC_ABINITIO_IGNORE_THE_REST-MOO18--1utg_-_9087_1_0 died with a computation error after 4201 seconds.

Error -1073741819 (0xffffffffc0000005)
it looks to have completed or at least started work on 17 models before crashing.

I've had a number of WUs with names like this:
rest3d85_ip40_2g3r.patchdock.3.pdb_0002_fa_dock.xml_score12_pert38_DOCK_9104

All 4 ran through 99 models in just 3hours. That will throw off work fetch for folks on Rosetta with longer runtime preference.

---

These 3 tasks, all named broker_lb_test2_hb*, failed on Mac after apparent successful completion due to some file error.

1421321
1421322
1421323

</stderr_txt>
<message>
<file_xfer_error>
<file_name>broker_lb_test2_hb_t363__IGNORE_THE_REST_9214_1_0_0</file_name>
<error_code>-161</error_code>
</file_xfer_error>

This task crashed on Mac with a segmentation violation.

1421317

Crash log is in the task file: here's the first bit:


Thread 0 Crashed:
0 ...etta_1.59_i686-apple-darwin 0x009579fe __ZNK4core7scoring7methods10VDW_Energy19residue_pair_energyERKNS_12conformation7ResidueES6_RKNS_4pose4PoseERKNS0_13ScoreFunctionERNS0_17TwoBodyEMapVectorE + 1534
1 ...etta_1.59_i686-apple-darwin 0x00189b81 __ZNK4core7scoring13ScoreFunctionclERNS_4pose4PoseE + 5171
2 ...etta_1.59_i686-apple-darwin 0x004e9985 __ZN9protocols8abinitio12AbrelaxMover5applyERN4core4pose4PoseE + 5993
3 ...etta_1.59_i686-apple-darwin 0x004d0a99 __ZN9protocols3jd214JobDistributor2goEN7utility7pointer10owning_ptrINS_5moves5MoverEEE + 4041
4 ...etta_1.59_i686-apple-darwin 0x00ace519 __ZN9protocols3jd219BOINCJobDistributor2goEN7utility7pointer10owning_ptrINS_5moves5MoverEEE + 41
5 ...etta_1.59_i686-apple-darwin 0x0010f73c __ZN9protocols8abinitio11Broker_mainEv + 812
6 ...etta_1.59_i686-apple-darwin 0x0000402c _main + 2532
7 ...etta_1.59_i686-apple-darwin 0x00001eee __start + 216
8 ...etta_1.59_i686-apple-darwin 0x00001e15 start + 41

I now have a minirosetta 1.59 workunit. Is it time to create a new thread for 1.59?

On this 1.59 workunit, I ran into the lockfile problem on structure _U16X13X_00019, but my wingman chose a shorter workunit length and therefore didn't even try that structure:

https://ralph.bakerlab.org/result.php?resultid=1422995

https://ralph.bakerlab.org/workunit.php?wuid=1260423

I use BOINC 6.2.28 under 32-bit Vista SP1 on that machine.

Although my machine still uses settings intended to check for the lockfile problem, I'm having to reboot my machine more often to get past problems with the router I'm using to allow a recently installed newer computer to reach the internet, and therefore less likely to actually see such problems.