| | 13 | In this example, I have committed a change at 4:46pm. About 5 minutes later, two builds were started (a third was also triggered, but a semaphore-like Lock caused it to be stalled for a few minutes, to reduce load on an underpowered buildslave). Those builds started by using the version-control system to update a local source tree, then they performed a compile step. Next, they ran unit tests, of which 270 tests passed and 6 were skipped. The "tw2.5-py2.3" builder had some number of warnings, probably deprecation warnings complaining about constructs that are discouraged in python-2.5 . However, the test step was not configured to flag these warnings, so the step's box is green. One of the builders performed an additional step called "pyflakes", which is a fast static analysis tool for python code to detect redefined or undefined names. This tool discovered 7 redefinitions, and marked the step orange to indicate that these warnings are important enough to pay attention to. |