On Mon, Oct 24, 2016 at 05:18:24PM -0600, Stephen Warren wrote: > On 10/24/2016 05:03 PM, Tom Rini wrote: > >On Mon, Oct 24, 2016 at 04:41:48PM -0600, Stephen Warren wrote: > > > >>From: Stephen Warren <[email protected]> > >> > >>Travis CI names sub-jobs after the first environment variable that is set > >>for a script. This doesn't produce meaningful results for any of the non- > >>buildman jobs. Add a dummy variable to give the jobs meaningful names. > >> > >>Signed-off-by: Stephen Warren <[email protected]> > > > >I'm not sure. This un-does in part killing off TEST_CMD as a hook. At > >the end of the day, imho, what is important from travis-ci are the > >emails it sends (which are starting and pass/fail/interrupted) and the > >other notifications. > > I don't believe I've ever received emails from Travis, although I > haven't used it in a while so perhaps it's a new feature.
Ah, https://docs.travis-ci.com/user/notifications#Email-notifications explains and it's setup by default to not spam uninterested parties. Which I think in turn means it also doesn't email interested parties easily, sadly. > Either way, I do like to look at the web UI to watch/check status > sometimes, and certainly would after a failure to track down the > problem, and this change makes the job list there possible to > interpret, whereas it isn't without it: > > https://travis-ci.org/swarren/u-boot/builds/170278972 Yeah, I spent a lot of time with the UI when I was doing the last series. And since it is indeed harder to get email notifications than I would like, this makes sense too. Reviewed-by: Tom Rini <[email protected]> -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
