Testing - reporting discuss what and why.

Message boards : Current tests : Testing - reporting discuss what and why.

To post messages, you must log in.

AuthorMessage
Profile anders n

Send message
Joined: 16 Feb 06
Posts: 166
Credit: 131,419
RAC: 0
Message 3385 - Posted: 23 Sep 2007, 6:53:36 UTC

Lets discuss how Ralph is working now, how YOU fell it should work and hopfully the staff will give there view as well.
ID: 3385 · Report as offensive    Reply Quote
Profile anders n

Send message
Joined: 16 Feb 06
Posts: 166
Credit: 131,419
RAC: 0
Message 3386 - Posted: 23 Sep 2007, 7:44:01 UTC

I start with a reminder that English is not my native language so sometimes it can sound harsh but it\'s the best I can do for now.

As a start I would like to know more about what the project get back from the Wu when a wu goes down(fails) .

What more info do they need from us to know why it failed.

Reporting back to us users from the projetct , how can it improve?

Should we be discussing credit issues , like not sending wu of certain sort to comupters that do them slow(to get optimal performans to the project and the users).

When there is a problem on Ralph that 1 or maybe 2 computers come up against how many computers on Rosetta will have the same troubel?

Anders n



ID: 3386 · Report as offensive    Reply Quote
Profile feet1st

Send message
Joined: 7 Mar 06
Posts: 313
Credit: 113,747
RAC: 96
Message 3387 - Posted: 23 Sep 2007, 12:55:45 UTC

One thing you might do to help report better information back would be to enable your firewall to contact Ralph directly. This so that the debug information can be sent back when a task crashes. Normally all communications are performed in BOINC, but such debug info. goes directly back to the project URL to report.

Unfortunately, my firewall requires I add the application name. So every new release on Ralph means I hope to remember to add it to my firewall settings.
ID: 3387 · Report as offensive    Reply Quote

Message boards : Current tests : Testing - reporting discuss what and why.



©2018 University of Washington
http://www.bakerlab.org