This wasn't good.

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

Segpipe errors on 3 tasks:

SIGSEGV: segmentation violation

Crashed executable name: minirosetta_1.64_i686-apple-darwin
built using BOINC library version 6.5.0
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.5.6 build 9G55
Tue Apr 28 18:55:15 2009

sh: /usr/bin/atos: No such file or directory
0 0x006b149b SIGPIPE: write on a pipe with no reader
1 0x0048754e SIGPIPE: write on a pipe with no reader
2 0x0215d2bb SIGPIPE: write on a pipe with no reader
3 0xffffffff SIGPIPE: write on a pipe with no reader
4 0x0017555a SIGPIPE: write on a pipe with no reader
5 0x0018b2ed SIGPIPE: write on a pipe with no reader
6 0x00517aae SIGPIPE: write on a pipe with no reader
7 0x004fce90 SIGPIPE: write on a pipe with no reader
8 0x00b4494b SIGPIPE: write on a pipe with no reader
9 0x00120021 SIGPIPE: write on a pipe with no reader
10 0x000048fd SIGPIPE: write on a pipe with no reader
11 0x000026ae SIGPIPE: write on a pipe with no reader
12 0x000025d5 SIGPIPE: write on a pipe with no reader
13 0x00000019
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xffffffe1 ebx: 0x02125802 ecx: 0xbfffb8cc edx: 0x020f11c6
edi: 0x00000000 esi: 0x00000000 ebp: 0xbfffb908 esp: 0xbfffb8cc
ss: 0x0000001f efl: 0x00000206 eip: 0x020f11c6 cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

1431298
1431297
1431275

WinXP, BOINC 5.10.45
this task called broker_lb_test3_hb_t288__IGNORE_THE_REST_9374_4_0 had a 24hr runtime preference, but ended after only 3hrs with these msgs:
ERROR: pose.fold_tree().is_cutpoint( *it )
ERROR:: Exit from: ....srcprotocolstopology_brokerTopologyBroker.cc line: 560

It finished as a "valid" "success" and so was not resent to get a second opinion on whether or not it would fail elsewhere.

---

not sure what happened here with broker_lb_test3_hb_t313__IGNORE_THE_REST_9385_5_0, but i just got home and rebooted the computer after a windows update and then the task just dies after something like a minute and 6 seconds.

Error msg: -1073741819 (0xffffffffc0000005)

The other one that took its place is running ok so far and the one before it is 23% into its work and is ok.

Are you sure 1.64 was adequately tested before releasing it to Rosetta@home? I've barely had any 1.64 workunits under Ralph@home at all.

Have Rosetta@home and Ralph@home switched roles in which of them tests new versions of applications first? I've already received several minirosetta 1.65 workunits from Rosetta@home, without seeing any sign that there have been any Ralph@home tests of that version at all.

not sure what happened here with broker_lb_test3_hb_t313__IGNORE_THE_REST_9385_5_0, but i just got home and rebooted the computer after a windows update and then the task just dies after something like a minute and 6 seconds.

Error msg: -1073741819 (0xffffffffc0000005)

The other one that took its place is running ok so far and the one before it is 23% into its work and is ok.

Did you remember to suspend BOINC during the Windows update and the reboot? I've recently seen something similar for a number of BOINC projects when I was unable to call up the BOINC manager program in order to suspend BOINC during a reboot.

Have Rosetta@home and Ralph@home switched roles in which of them tests new versions of applications first? I've already received several minirosetta 1.65 workunits from Rosetta@home, without seeing any sign that there have been any Ralph@home tests of that version at all.

INteresting... me too ... I wonder if they just screwed the version number where 1.65 is 1.64 with a new dress ...

A couple of failures of version 1.65 (doesn't seem to be a specific thread for it yet) on Mac apparently somewhere in task termination as it seemed to run for a normal length of time.

1436213
1436214

Crashed executable name: minirosetta_1.65_i686-apple-darwin
built using BOINC library version 6.5.0
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.4.11 build 8S2167
Sat May 2 20:35:24 2009

Thread 0 Crashed:
0 ...etta_1.65_i686-apple-darwin 0x00edd115 __ZN7utility7signals9SignalHubIvN4core12conformation7signals16DestructionEventEE11send_signalES5_ + 2353
1 ...etta_1.65_i686-apple-darwin 0x00021b39 __ZN4core12conformation12ConformationD1Ev + 7373
2 ...etta_1.65_i686-apple-darwin 0x000784c8 __ZN4core4pose4PoseD1Ev + 4652
3 ...etta_1.65_i686-apple-darwin 0x004fc6a4 __ZN9protocols3jd214JobDistributor2goEN7utility7pointer10owning_ptrINS_5moves5MoverEEE + 1730
4 ...etta_1.65_i686-apple-darwin 0x00b44a7b __ZN9protocols3jd219BOINCJobDistributor2goEN7utility7pointer10owning_ptrINS_5moves5MoverEEE + 41
5 ...etta_1.65_i686-apple-darwin 0x0011fdc1 __ZN9protocols8abinitio11Broker_mainEv + 1543
6 ...etta_1.65_i686-apple-darwin 0x0000469d _main + 2805
7 ...etta_1.65_i686-apple-darwin 0x0000244e __start + 216
8 ...etta_1.65_i686-apple-darwin 0x00002375 start + 41

Have Rosetta@home and Ralph@home switched roles in which of them tests new versions of applications first? I've already received several minirosetta 1.65 workunits from Rosetta@home, without seeing any sign that there have been any Ralph@home tests of that version at all.

INteresting... me too ... I wonder if they just screwed the version number where 1.65 is 1.64 with a new dress ...

They had to correct the upload problems

If you go to the homepage of both Ralph and Rosetta and click the "applications" link, you can see it was posted to Ralph first.

---