Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 
World Community Grid Forums
  Category: Beta Testing
  Forum: Beta Test Support Forum
  Thread: New Beta Test – October 8, 2019 [Issues thread]

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 33
Posts: 33   Pages: 4   [ Previous Page | 1 2 3 4 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 10501 times and has 32 replies Next Thread
Crystal Pellet
Veteran Cruncher
Joined: May 21, 2008
Post Count: 1403
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test – October 8, 2019 [Issues thread]
Thanks Jonathan,

That explains it.
I did not have a close watch at the version numbers of the wingmen. I did not expect workunits with a combination of 2 versions.
[Oct 17, 2019 7:31:27 PM]   Link   Report threatening or abusive post: please login first  Go to top 
masteraip
Advanced Cruncher
Bulgaria
Joined: Jul 27, 2016
Post Count: 71
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test – October 8, 2019 [Issues thread]
got 1 from 7.27, still 5 hours remaining to complete
----------------------------------------
Personal stats Team stats
[Oct 18, 2019 7:18:08 AM]   Link   Report threatening or abusive post: please login first  Go to top 
DrMason
Senior Cruncher
Joined: Mar 16, 2007
Post Count: 153
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test – October 8, 2019 [Issues thread]
Got some 7.27s and they seem to be crunching fine so far.

Have an interesting test case when it comes to credit. It seems anything above 20 hours results in the fixed 350.7 credit, whereas anything below that is almost twice that.

BETA_ ARP1_ 0002656_ 000_ 3-- BOINCLAB3 Pending Verification 10/17/19 18:04:33 10/18/19 14:37:02 19.20 / 19.37 589.9 / 0.0
BETA_ ARP1_ 0002121_ 000_ 3-- BOINCLAB3 Pending Verification 10/17/19 04:26:32 10/18/19 01:26:33 20.26 / 20.35 350.7 / 0.0

19.37 hrs = 589.9 pts (or ~30.5 pts/hr); 20.35 hrs = 350.7 (or ~17.25 pts/hr)

I don't really care about the points in BETA, and no matter what I'll be contributing to the project when it comes out, but is there plans for a fix for the actual project release? I know it's been discussed, but I'm not sure where it left off. I could see a lot of people running slightly older (or server) hardware feeling like their contributions weren't as rewarded. Unless of course the goal is to target and incentivize only the people on the bleeding edge to crunch laughing .
----------------------------------------

----------------------------------------
[Edit 1 times, last edit by DrMason at Oct 18, 2019 4:33:57 PM]
[Oct 18, 2019 4:33:15 PM]   Link   Report threatening or abusive post: please login first  Go to top 
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2346
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test – October 8, 2019 [Issues thread]
Changed from Pending Validation to Too Late after Wingman 4 returned an Error:
Result Name               OS              AVN Status   Sent Time         Due / Return Time CPUh  Claimed/Gr.
BETA_ARP1_0002667_000_4-- Linux CentOS    727 Error    10/18/19 09:34:41 10/18/19 16:22:25  6.77   215.0/0.0
BETA_ARP1_0002667_000_3-- Linux Fedora    727 Too Late 10/17/19 09:06:49 10/18/19 09:34:27 23.89   350.7/0.0
BETA_ARP1_0002667_000_2-- Linux LinuxMint 726 Too Late 10/16/19 15:07:04 10/17/19 09:06:36 16.76   350.7/0.0
BETA_ARP1_0002667_000_0-- Linux LinuxMint 726 Too Late  10/9/19 15:17:48 10/10/19 14:50:32 14.75   350.7/0.0
BETA_ARP1_0002667_000_1-- Linux Ubuntu    726 Too Late  10/9/19 15:17:46 10/13/19 15:50:06 52.91   350.7/0.0
[Generated by wcgformat]

My Result Log:

Result Name: BETA_ ARP1_ 0002667_ 000_ 3--
<core_client_version>7.16.1</core_client_version>
<![CDATA[
<stderr_txt>
INFO: Initializing
INFO: No state to restore. Start from the beginning.
Starting WRFMain
[13:55:32] INFO: Checkpoint taken at 2018-07-01_06:00:00
[17:36:18] INFO: Checkpoint taken at 2018-07-01_12:00:00
[21:03:19] INFO: Checkpoint taken at 2018-07-01_18:00:00
[23:28:51] INFO: Checkpoint taken at 2018-07-02_00:00:00
[02:15:56] INFO: Checkpoint taken at 2018-07-02_06:00:00
[05:45:35] INFO: Checkpoint taken at 2018-07-02_12:00:00
[09:08:55] INFO: Checkpoint taken at 2018-07-02_18:00:00
[11:30:07] INFO: Checkpoint taken at 2018-07-03_00:00:00
INFO: Simulation complete compressing output.
11:32:31 (9676): called boinc_finish(0)

</stderr_txt>
]]>
====================
Wingman 4's Result Log:

Result Name: BETA_ ARP1_ 0002667_ 000_ 4--
<core_client_version>7.15.0</core_client_version>
<![CDATA[
<message>
aborting on client exit</message>
<stderr_txt>
INFO: Initializing
INFO: No state to restore. Start from the beginning.
Starting WRFMain
[11:06:49] INFO: Checkpoint taken at 2018-07-01_06:00:00
[13:06:55] INFO: Checkpoint taken at 2018-07-01_12:00:00
[14:50:41] INFO: Checkpoint taken at 2018-07-01_18:00:00
[15:52:58] INFO: Checkpoint taken at 2018-07-02_00:00:00

</stderr_txt>
]]>
[Oct 18, 2019 6:10:26 PM]   Link   Report threatening or abusive post: please login first  Go to top 
hchc
Veteran Cruncher
USA
Joined: Aug 15, 2006
Post Count: 865
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test – October 8, 2019 [Issues thread]
@adriverhoef:

I also had a wingman on CentOS running BOINC 7.15.0 error out.

Link: https://www.worldcommunitygrid.org/ms/device/....do?workunitId=1316680675

OS Version: CentOS Linux release 7.4.1708 (Core) [3.10.0-693.21.1.el7.x86_64|libc 2.17 (GNU libc)]

Wingman's Result Log:

Result Name: BETA_ ARP1_ 0002578_ 000_ 3--
<core_client_version>7.15.0</core_client_version>
<![CDATA[
<message>
aborting on client exit</message>
]]>

I think maybe the same device, probably a server that's configured to abort on client exit, is trashing a lot of beta work units. Probably the same device for both of us!
----------------------------------------
  • i5-7500 (Kaby Lake, 4C/4T) @ 3.4 GHz
  • i5-4590 (Haswell, 4C/4T) @ 3.3 GHz
  • i5-3570 (Broadwell, 4C/4T) @ 3.4 GHz
[Oct 18, 2019 10:01:17 PM]   Link   Report threatening or abusive post: please login first  Go to top 
adriverhoef
Master Cruncher
The Netherlands
Joined: Apr 3, 2009
Post Count: 2346
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test – October 8, 2019 [Issues thread]
@hchc: I have selected the OS Version of Wingman 4 on my end below.
Result Name               OS           OS Version                                                                             AVN Status
BETA_ARP1_0002667_000_4-- Linux CentOS CentOS Linux release 7.4.1708 (Core) [3.10.0-693.21.1.el7.x86_64|libc 2.17 (GNU libc)] 727 Error
[Generated by wcgformat]

Yes, that's exactly the same OS Version. As you were saying: probably the same device.

UPDATE:
Found out I picked up another one presumably from that same device. This time it's Wingman 3, while mine is _2:
Result Name               OS           AVN Status  Sent Time         Due / Return Time CPUh  Claimed/Gr.
BETA_ARP1_0002497_000_4-- Linux        727 Valid   10/17/19 18:29:27 10/18/19 20:26:58 25.50   350.7/350.7
BETA_ARP1_0002497_000_3-- Linux CentOS 727 Error   10/17/19 13:50:13 10/17/19 18:29:22  4.64   147.5/0.0
BETA_ARP1_0002497_000_2-- Linux Fedora 727 Valid   10/16/19 15:49:23 10/17/19 13:49:59 14.73   350.7/350.7
BETA_ARP1_0002497_000_1-- Linux Ubuntu 726 Invalid  10/9/19 15:15:41 10/10/19 11:55:08 10.15   425.2/350.7
BETA_ARP1_0002497_000_0-- Linux Ubuntu 726 Invalid  10/9/19 15:15:39 10/10/19 16:54:02 16.63   350.7/350.7

Result Name               OS           OS Version                                                                             AVN Status
BETA_ARP1_0002497_000_3-- Linux CentOS CentOS Linux release 7.4.1708 (Core) [3.10.0-693.21.1.el7.x86_64|libc 2.17 (GNU libc)] 727 Error
[Generated by wcgformat]

Result Log

Result Name: BETA_ ARP1_ 0002497_ 000_ 3--
<core_client_version>7.15.0</core_client_version>
<![CDATA[
<message>
aborting on client exit</message>
<stderr_txt>
INFO: Initializing
INFO: No state to restore. Start from the beginning.
Starting WRFMain
[15:08:40] INFO: Checkpoint taken at 2018-07-01_06:00:00
[16:58:03] INFO: Checkpoint taken at 2018-07-01_12:00:00

</stderr_txt>
]]>
----------------------------------------
[Edit 3 times, last edit by adriverhoef at Oct 19, 2019 1:12:35 PM]
[Oct 18, 2019 10:15:10 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: New Beta Test – October 8, 2019 [Issues thread]
For most work units the initial results _0 and _1 are 7.26 and will eventually go invalid when we get two results from 7.27 and they validate. I have checked the output for 7.27 and the bug is gone, I am not saying there might not be other issues but we don't have any redundant results from 7.27 back yet.
Thanks,
armstrdj

Just curious how the below set is ever going to validate, where my 'in progress' copy is the only one running on 7.27 and the distribution cap is AFAIK 5.

BETA_ ARP1_ 0002214_ 000_ 4-- Microsoft Windows 10 Core x64 Edition, (10.00.18362.00) - In Progress 10/19/19 17:25:05 10/22/19 04:13:05 0.00 0.0 / 0.0
BETA_ ARP1_ 0002214_ 000_ 3-- Microsoft Windows 8.1 Professional x64 Edition, (06.03.9600.00) 726 Pending Verification 10/16/19 15:11:01 10/19/19 17:24:48 17.47 350.7 / 0.0
BETA_ ARP1_ 0002214_ 000_ 2-- Microsoft Windows Server 2008 "R2" Enterprise x64 Edition, Service Pack 1, (06.01.7601.00) 726 Pending Verification 10/9/19 15:16:04 10/10/19 22:53:02 31.02 350.7 / 0.0
BETA_ ARP1_ 0002214_ 000_ 1-- Microsoft Windows 10 Education x64 Edition, (10.00.17763.00) 726 Pending Verification 10/9/19 15:13:32 10/10/19 14:15:09 14.41 578.8 / 0.0
BETA_ ARP1_ 0002214_ 000_ 0-- Microsoft Windows 8.1 x64 Edition, (06.03.9600.00) 726 Error 10/9/19 15:13:29 10/9/19 15:15:57

Edit: As suspected, the sole return with 7.27 caused a 'validation state 3, Too many errors'. Why all got change to 'Too Late' in status in unknown too me.
----------------------------------------
[Edit 2 times, last edit by Former Member at Oct 21, 2019 8:02:08 AM]
[Oct 20, 2019 7:59:07 PM]   Link   Report threatening or abusive post: please login first  Go to top 
vepaul
Senior Cruncher
Belgium
Joined: Nov 17, 2004
Post Count: 261
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test – October 8, 2019 [Issues thread]
One arrived a few days ago.
[Oct 20, 2019 9:39:46 PM]   Link   Report threatening or abusive post: please login first  Go to top 
JSYKES
Senior Cruncher
Joined: Apr 28, 2007
Post Count: 206
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test – October 8, 2019 [Issues thread]
I received a 7.27 WU but it wouldn't process beyond about 20% before 'an error' appeared to force a restart.... - I left it to 'play about' up to the point where it was clearly going to be a waste of time (about 3hrs before return time) when I aborted it - showing it still had another 22hrs to run, despite only processing 15% in about 6hrs.... wishful thinking???!!!!
I now see that every other WU in this set was 'too late'.
Was there something fundamentally wrong with the ARP beta WU's issued?
----------------------------------------
[Oct 22, 2019 10:32:54 AM]   Link   Report threatening or abusive post: please login first  Go to top 
armstrdj
Former World Community Grid Tech
Joined: Oct 21, 2004
Post Count: 695
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: New Beta Test – October 8, 2019 [Issues thread]
There was not anything wrong with the work units. The issue was that they initially ran under 7.26 which had a bug so not all work units had two copies that ran under 7.27 and some not by the deadline. The average runtime for these runs are around 24 hours cpu time.

Thanks,
armstrdj
[Oct 22, 2019 3:11:43 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 33   Pages: 4   [ Previous Page | 1 2 3 4 | Next Page ]
[ Jump to Last Post ]
Post new Thread