Changes between Version 14 and Version 15 of ReportBugs
- Timestamp:
- Apr 19, 2011, 11:35:40 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ReportBugs
v14 v15 5 5 The following information tells BOINC Alpha Testers (and anyone else who wants to help) how to report hard bugs, 6 6 so that we can fix them even if we can't reproduce them. 7 8 == Background ==9 7 10 8 The BOINC client software consists of two programs: the '''core client''', … … 24 22 When BOINC does something wrong, one or more of these files often contain information that allows BOINC developers to easily find and fix the problem. 25 23 26 == Reporting hard bugs ==27 24 Report hard bugs by email, either to the [mlist:boinc_alpha boinc_alpha] email list or directly to [ProjectPeople David and Rom]. 28 25 '''Note: when you post to boinc_alpha, attachments are stripped from your email; include text inline rather than as attachments. … … 53 50 Please edit the file to remove old entries, so that we don't get confused by them. 54 51 52 == The BOINC Client Emulator == 55 53 56 == Incorrect behavior == 54 Problems involving task scheduling typically depend on 55 the specific computer and the projects to which it's attached. 56 This makes it hard for BOINC developers to reproduce such problems. 57 58 The best way to report such problems is to reproduce them using the 59 [http://boinc.berkeley.edu/dev/sim_web.php BOINC Client Emulator], 60 then send us a link to the result. 61 62 == Message logs == 57 63 If BOINC behaves incorrectly, we usually need the core client's message log to figure out what's going on. 58 64 The message log describes what the core client is doing. 59 65 It's identical to what's shown in the Messages tab of the Manager. 60 By default the core client writes only a few messages. More detailed messages are enabled by turning on [ClientMessages logging flags]. 66 By default the core client writes only a few messages. 67 More detailed messages are enabled by turning on [ClientMessages logging flags]. 61 68 This is done by editing the file `cc_config.xml` in your BOINC directory. 62 69 For example, the following turns on the `task_debug` and `cpu_sched` flags (1 turns a flag on; 0 or unspecified turns it off): … … 85 92 86 93 Some common problem types, and the suggested logging flags, are listed below. 87 You should also check the [ ClientMessages complete list of logging flags].94 You should also check the [http://boinc.berkeley.edu/wiki/Client_configuration#Logging_flags complete list of logging flags]. 88 95 89 === BOINC gets too much or too little work === 96 BOINC gets too much or too little work 90 97 91 98 {{{ … … 93 100 }}} 94 101 95 === BOINC thinks apps are running but they aren't === 102 BOINC thinks apps are running but they aren't 96 103 97 104 {{{ … … 101 108 }}} 102 109 103 === CPU benchmark problems === 110 CPU benchmark problems 104 111 105 112 {{{ … … 107 114 }}} 108 115 109 === Bad CPU scheduling decisions === 116 Bad task scheduling decisions 110 117 111 118 {{{ … … 115 122 }}} 116 123 117 === Memory usage preferences === 124 Memory usage and non-BOINC CPU usage 118 125 119 126 {{{ … … 121 128 }}} 122 129 123 === File transfer problems === 130 File transfer problems 124 131 125 132 {{{ … … 128 135 }}} 129 136 130 === Screensaver problems === 137 Screensaver problems 131 138 132 139 {{{ … … 134 141 }}} 135 142 136 === Applications not reporting CPU time, fraction done correctly === 143 Applications not reporting CPU time, fraction done correctly 137 144 138 145 {{{
