Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 
World Community Grid Forums
  Category: Support
  Forum: Android Support Forum
  Thread: Suspicious "Too Late"

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 5
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1641 times and has 4 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Suspicious "Too Late"
TODAY'S DATE: 28 FEB 2015
OET1_ 0000470_ xEBGP-L_ rig_ 34631_ 0--
android_7e66c67b
Too Late <------------------SUSPICIOUS
2/18/15 03:00:59
2/19/15 02:06:42 <-----------SEE?
5.11 / 5.12
18.3 / 0.0

https://secure.worldcommunitygrid.org/ms/devi....do?workunitId=1315276097

---
Result Log

Result Name: OET1_ 0000470_ xEBGP-L_ rig_ 34631_ 0--
<core_client_version>7.4.41</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[15:59:15] Number of tasks = 1
[15:59:15] Running task 0,CPU time at start of task 0 was 0.000000
[15:59:15] ./ZINC01577565.pdbqt size = 20 6 ../../projects/www.worldcommunitygrid.org/oet1.xEBGP-L_rig.pdbqt size = 2470 0
[21:06:33] Finished task #0 cpu time used 18390.170000
21:06:33 (11033): called boinc_finish(0)

</stderr_txt>
]]>


Result Log

Result Name: OET1_ 0000470_ xEBGP-L_ rig_ 34631_ 1--
<core_client_version>7.4.41</core_client_version>


Result Log

Result Name: OET1_ 0000470_ xEBGP-L_ rig_ 34631_ 2--
<core_client_version>7.2.15</core_client_version>
<![CDATA[
<message>
process got signal 11
</message>
<stderr_txt>

</stderr_txt>
]]>


Result Log

Result Name: OET1_ 0000470_ xEBGP-L_ rig_ 34631_ 3--
<core_client_version>7.4.14</core_client_version>
<![CDATA[
<message>
process got signal 11
</message>
<stderr_txt>

</stderr_txt>
]]>


Result Log

Result Name: OET1_ 0000470_ xEBGP-L_ rig_ 34631_ 4--
<core_client_version>7.4.37</core_client_version>
<![CDATA[
<message>
process got signal 11
</message>
<stderr_txt>

</stderr_txt>
]]>


Result Log

Result Name: OET1_ 0000470_ xEBGP-L_ rig_ 34631_ 5--
<core_client_version>7.4.37</core_client_version>
<![CDATA[
<message>
process got signal 11
</message>
<stderr_txt>

</stderr_txt>
]]>
---
[Feb 28, 2015 7:46:30 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Suspicious "Too Late"
Not, as when you look in the Result Status work unit detail you'll probably find 5 other copies have ended with error [oh yes they did]. This is when any single copy that did not fail becomes 'Too Late' (to find any verifying companion to validate against). Credit is fully granted for the work done just before the unit is removed to the 'take out' list.
----------------------------------------
[Edit 1 times, last edit by Former Member at Feb 28, 2015 7:53:22 PM]
[Feb 28, 2015 7:51:51 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Suspicious "Too Late"
... any single copy that did not fail becomes
'Too Late' (to find any verifying companion to validate against).
Credit is fully granted for the work done just before
the unit is removed to the 'take out' list.

So, poor choice of wording, and overloading for
two different situations.

How about, "Unverified/credited"? ..since "Too Late" it wasn't.
[Feb 28, 2015 8:06:11 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Suspicious "Too Late"
You must be #679 who's coming with a proposal to change, when 'Too Late' is just as the FAQ explains, kind of a stop gap. There's no condition available in the BOINC server software, provided by Berkeley, to fill this void. Until they will, this is what it is.
[Feb 28, 2015 8:17:38 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Suspicious "Too Late"
The result harvest of the past 24 hours, including a "Too many errors on Wingmen" aka "Too Late". 24 returned, 2 Valid, 2 PV, 1 TL, 19 SIGSEGV Signal error 193. Yes, there was a contribution to fight Ebola, a drop on the boiler plate though. sad

Name ResultsAvailable ResultsReturned Offset AppName Status CpuTime ElapsedTime Efficiency NetName Outco me ReceivedTime
OET1_0000404_xEBGP-F_rig_85703_3 292 250 0 oet1 Too Many Errors on Wingmen 5,6951 5,9794 95,24% Tablet_01 (Work) 1 11-03-15 14:05
OET1_0000404_xEBGP-F_rig_88419_0 292 250 0 oet1 Pending Validation 5,3565 5,6169 95,36% Tablet_01 (Work) 1 11-03-15 13:43
OET1_0000404_xEBGP-F_rig_28890_4 292 250 0 oet1 Server Aborted 0,0000 0,0000 0,00% Tablet_01 (Work) 3 11-03-15 13:34
OET1_0000404_xEBGP-F_rig_25907_0 292 250 0 oet1 Pending Validation 5,1711 5,4301 95,23% Tablet_01 (Work) 1 11-03-15 13:32
OET1_0000403_xEBGP-F_rig_77205_1 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0000 0,0000 0,00% Tablet_01 (Work) 3 11-03-15 07:52
OET1_0000403_xEBGP-F_rig_71190_2 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0000 0,0000 0,00% Tablet_01 (Work) 3 11-03-15 07:47
OET1_0000403_xEBGP-F_rig_22055_0 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0042 0,0047 90,33% Tablet_01 (Work) 3 11-03-15 07:43
OET1_0000402_xEBGP-F_rig_68079_2 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0003 0,0003 100,00% Tablet_01 (Work) 3 11-03-15 07:38
OET1_0000403_xEBGP-F_rig_51988_3 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0003 0,0006 50,49% Tablet_01 (Work) 3 11-03-15 07:34
OET1_0000401_xZAGP-L_rig_19910_5 292 250 0 oet1 Valid 3,2699 3,3313 98,16% Tablet_01 (Work) 1 11-03-15 07:00
OET1_0000403_xEBGP-F_rig_0188_5 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0048 0,0048 100,00% Tablet_01 (Work) 3 11-03-15 06:50
OET1_0000403_xEBGP-F_rig_17826_0 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0000 0,0000 0,00% Tablet_01 (Work) 3 11-03-15 04:55
OET1_0000402_xEBGP-F_rig_86467_0 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0052 0,0055 94,20% Tablet_01 (Work) 3 11-03-15 04:45
OET1_0000395_xZAGP-FA_rig_6357_0 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0000 0,0000 0,00% Tablet_01 (Work) 3 11-03-15 04:31
OET1_0000402_xEBGP-F_rig_86451_0 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0000 0,0000 0,00% Tablet_01 (Work) 3 11-03-15 04:21
OET1_0000402_xEBGP-F_rig_84431_0 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0055 0,0055 99,75% Tablet_01 (Work) 3 11-03-15 03:56
OET1_0000395_xZAGP-FA_rig_63561_0 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 1,9398 2,0277 95,66% Tablet_01 (Work) 3 11-03-15 03:33
OET1_0000395_xZAGP-FA_rig_17596_0 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0019 0,0019 100,00% Tablet_01 (Work) 3 11-03-15 03:29
OET1_0000402_xEBGP-F_rig_8442_0 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0000 0,0000 0,00% Tablet_01 (Work) 3 11-03-15 03:29
OET1_0000395_xZAGP-FA_rig_63331_1 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0020 0,0020 97,96% Tablet_01 (Work) 3 11-03-15 02:58
OET1_0000395_xZAGP-FA_rig_63324_1 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 4,3940 4,5519 96,53% Tablet_01 (Work) 3 11-03-15 00:37
OET1_0000395_xZAGP-FA_rig_61838_2 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 4,2532 4,3895 96,89% Tablet_01 (Work) 3 11-03-15 00:32
OET1_0000395_xZAGP-FA_rig_1726_0 292 250 0 oet1 Valid 7,8751 8,2626 95,31% Tablet_01 (Work) 1 10-03-15 18:52
OET1_0000395_xZAGP-FA_rig_35528_1 292 250 0 oet1 Signal Error 193/SIGSEGV Code 11 0,0016 0,0020 81,21% Tablet_01 (Work) 3 10-03-15 15:41
[Mar 11, 2015 4:01:31 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread