14 | | Testers must subscribe to the [mlist:boinc_alpha boinc_alpha email list]. (You don't need to be a tester to subscribe to this list). |
| 17 | == The BOINC Alpha project == |
| 18 | |
| 19 | Testers must log in to the [http://isaac.ssl.berkeley.edu/alpha/ BOINC Alpha project] |
| 20 | to report test results. |
| 21 | It'a also a BOINC project, but usually it doesn't have any jobs, and you don't need to attach your client to it. |
| 22 | |
| 23 | == The BOINC Alpha email list == |
| 24 | |
| 25 | Testers must subscribe to the [mlist:boinc_alpha boinc_alpha email list]. |
| 26 | (You don't need to be a tester to subscribe to this list). |
18 | | Periodically (every couple of weeks, sometimes more) we'll send an announcement on the email list, asking alpha testers to download and test a specific new release of BOINC. You can find these releases on the [/download_all.php?dev=1 download page]. Please try to report test results within two days of receiving the email. |
| 30 | Periodically (every couple of weeks, sometimes more) we'll send an announcement on the email list, |
| 31 | asking alpha testers to download and test a specific new release of BOINC. |
| 32 | You can find these releases on the [/download_all.php?dev=1 BOINC download page]. |
| 33 | Please try to report test results within two days of receiving the email. |
26 | | Depending on what you're testing, you can select which project(s) to attach to: |
27 | | |
28 | | * The BOINC Alpha project (this one) has tasks with large input and output files (4.5 MB each) and that use about 1 minute of CPU time. This is useful for testing file upload/download, and for testing things that happen on task completion. '''You don't need to attach to this project to be an Alpha Tester. Please do not stay attached to this project for long periods.''' |
29 | | * You can use the Cunning Plan project (http://isaac.ssl.berkeley.edu/cplan) for tests that involve creating accounts. |
30 | | * You can use other projects (SETI@home, Einstein@home, CPDN) for other purposes. |
31 | | |
32 | | If at any time you experienced problems with BOINC that are not exercised by any of these tests, please post to the [mlist:boinc_alpha boinc_alpha@ssl.berkeley.edu email list]. |
| 44 | The client software under test may have bugs that wipe out tasks in progress, |
| 45 | so consider using a different data directory when you install the test software. |
36 | | * Report test results through the [http://isaac.ssl.berkeley.edu/alpha/test_form.php web-based interface]. |
37 | | * If you see a major problem and have time: |
38 | | * Set the relevant [userw:Client_configuration log flags] |
39 | | * Post a description of the problem, together with the message logs, to the boinc_alpha@ssl.berkeley.edu email list. |
40 | | * For more details, see [ReportBugs Reporting Hard Bugs]. |
41 | | * If you're not sure whether something is a problem, post to the boinc_alpha@ssl.berkeley.edu email list. |
42 | | * If a problem persists across multiple releases, you can submit bug reports to the [WikiStart BOINC bug database], or send email to the relevant [DevProcess area owner]. |
| 49 | Report results through the [http://isaac.ssl.berkeley.edu/alpha/test_form.php web-based interface]. |
| 50 | |
| 51 | If you find a bug or unexpected bahavior in the BOINC client, |
| 52 | it will help us a lot if you can tell BOINC to generate more detailed |
| 53 | messages, and then post a message to boinc_alpha describing the problem |
| 54 | and including the message log. |
| 55 | To do this, use a text editor like Notepad to create a file |
| 56 | '''cc_config.xml''' in your BOINC data directory. |
| 57 | It has the following form: |
| 58 | {{{ |
| 59 | <cc_config> |
| 60 | <log_flags> |
| 61 | <work_fetch_debug>1</work_fetch_debug> |
| 62 | </log_flags> |
| 63 | </cc_config> |
| 64 | }}} |
| 65 | The '''work_fetch_debug''' flag tells BOINC to generate detailed |
| 66 | messages about how it decides when to ask projects for jobs. |
| 67 | There are [userw:Client_configuration lots of other flags] for other types of problems. |
| 68 | |
| 69 | |
| 70 | For more details on reporting bugs, see [ReportBugs Reporting Hard Bugs]. |
| 71 | |
| 72 | If you're not sure whether something is a problem, post to the boinc_alpha@ssl.berkeley.edu email list. |
| 73 | |
| 74 | If a problem persists across multiple releases, |
| 75 | you can submit bug reports to the [WikiStart BOINC bug database], |
| 76 | or send email to the relevant [DevProcess area owner]. |