| 252 | |
| 253 | |
| 254 | = What happens when builds/tests fail ? = |
| 255 | |
| 256 | |
| 257 | Failures result in notification emails and an entry on the timeline. Following the |
| 258 | link in the email gets you to the build status page, such as : |
| 259 | * http://dayabay.ihep.ac.cn/tracs/dybsvn/build/dybinst/3800 |
| 260 | |
| 261 | Examining the error reporting there and on the summary page |
| 262 | * http://dayabay.ihep.ac.cn/tracs/dybsvn/build/dybinst |
| 263 | |
| 264 | will tell you which '''step''' of the build/tests failed. |
| 265 | |
| 266 | You can confirm the error by running pkg tests via dybinst, eg for '''rootiotest''' |
| 267 | {{{ |
| 268 | ./dybinst trunk tests rootiotest |
| 269 | }}} |
| 270 | and investigate futher by getting into the environment and directory of the pkg running the tests |
| 271 | {{{ |
| 272 | nosetests -v |
| 273 | }}} |
| 274 | |
| 275 | |
| 276 | |
| 277 | |
| 278 | |
| 279 | |
| 280 | |
| 281 | |
| 282 | |