Welcome to MilkyWay@home

Beta work


Advanced search

Message boards : Number crunching : Beta work
Message board moderation

To post messages, you must log in.

AuthorMessage
ProfileJLDun
Avatar

Send message
Joined: 17 Nov 07
Posts: 77
Credit: 105,097
RAC: 212
100 thousand credit badge10 year member badge
Message 1006 - Posted: 11 Dec 2007, 5:24:15 UTC

12/10/2007 11:00:47 PM||log flags: task, file_xfer, sched_ops, unparsed_xml
12/10/2007 11:12:45 PM||[unparsed_xml] PROJECT::parse_account(): unrecognized: <allow_beta_work>1</allow_beta_work>
12/10/2007 11:12:45 PM||[unparsed_xml] parse_account_file_venue(): unrecognized: <allow_beta_work>1</allow_beta_work>
Is there any Beta work planned 'soon'?
ID: 1006 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 1011 - Posted: 11 Dec 2007, 14:47:16 UTC - in response to Message 1006.  

12/10/2007 11:00:47 PM||log flags: task, file_xfer, sched_ops, unparsed_xml
12/10/2007 11:12:45 PM||[unparsed_xml] PROJECT::parse_account(): unrecognized: 1
12/10/2007 11:12:45 PM||[unparsed_xml] parse_account_file_venue(): unrecognized: 1
Is there any Beta work planned 'soon'?


once we get the php bugs on the webpage, and the last memory leaks in the application fixed (as well as the problem with boinc hanging when it gets suspended sometimes), we'll probably move into beta.
ID: 1011 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileJLDun
Avatar

Send message
Joined: 17 Nov 07
Posts: 77
Credit: 105,097
RAC: 212
100 thousand credit badge10 year member badge
Message 1023 - Posted: 12 Dec 2007, 5:11:48 UTC - in response to Message 1011.  

we'll probably move into beta.

Huh; I forgot MaH was still in Alpha... ;-p
When I wrote the previous post, I was thinking of Seti@Home, which has a separate site for Beta-App development.
ID: 1023 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
zombie67 [MM]
Avatar

Send message
Joined: 29 Aug 07
Posts: 115
Credit: 258,901,533
RAC: 89,877
200 million credit badge10 year member badge
Message 1034 - Posted: 13 Dec 2007, 5:43:39 UTC - in response to Message 1023.  

Huh; I forgot MaH was still in Alpha... ;-p
When I wrote the previous post, I was thinking of Seti@Home, which has a separate site for Beta-App development.

No need for separate sites with the modern BOINC server SW. There is now the ability to turn on/off a user setting, to allow Beta apps within the same project.

ID: 1034 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileJLDun
Avatar

Send message
Joined: 17 Nov 07
Posts: 77
Credit: 105,097
RAC: 212
100 thousand credit badge10 year member badge
Message 1101 - Posted: 16 Dec 2007, 9:01:28 UTC - in response to Message 1034.  

And from The Story of the Hare who Lost His Spectacles:
...
We have two redundant schedulers on bruno/ptolemy, both running the exact same executable (mounted from the same NAS, no less), on the exact same linux OS/kernel. One was sending work, the other was not. By "not" I mean there was work available, but something was causing the schedule processes on bruno to wrongly think that the work wasn't suitable for sending out.
...
We checked everything: ifconfigs, MTU sizes, DNS records, router settings, routing tables, apache configurations, everything. We rebooted switches and servers to no avail. We had no choice but to begin questioning the actual code that has been working for months and happens to still be working perfectly on ptolemy.

Jeff attached a debugger to the many scheduler cgi processes and eventually spotted something odd. Why was the scheduler tagging the ready-to-send result in the shared memory (which is filled by the feeder) as "beta" results? We looked on ptolemy. There were not tagged as "beta" there. A clue!

Scheduler code was pored through and digested and it was determined this was indeed the heart of the problem - results tagged as "beta" were not to be sent out to regular clients asking for non-beta work. So bruno's refused to send any of these results out - it was erroneously thinking these were all "beta" results. But why?!
...
...
but before getting lost down that road we put in a one-line hack which forces beta to be "0" no matter what bogus values get put in the oversized C struct,
...

ID: 1101 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Beta work

©2019 Astroinformatics Group