Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Unify buildevnts indicating build completion | Klaus Aehlig | 2017-09-19 |
| | | | | | | | ...by factoring out the common code parts. Change-Id: I2ead39ea218dd535af9684a81a7bbe29b558aa27 PiperOrigin-RevId: 169106854 | ||
* | BEP: Upon missing test targets, still generate a finished event | Klaus Aehlig | 2017-09-15 |
| | | | | | | | | If a test command is aborted as no tests are found, still generate a BuildComplete event in the sequence of build events to properly report the exit status. Change-Id: Id811a116b309a26e67332947b3a5c66363b1ce9c PiperOrigin-RevId: 168703240 | ||
* | BEP: always close stream, even if aborted due to missing tests | Klaus Aehlig | 2017-09-12 |
If testing is requested, but no tests are found, the build is aborted. Ensure that even in this case the steam of build events is internally closed (i.e., all announced events are reported, the last event is marked as such). Change-Id: I88763ed6ccd7793deedbcb3428df7e8d289efa23 PiperOrigin-RevId: 168364127 |