On Sun, Jan 14, 2018 at 11:43:05AM +0100, SZEDER Gábor wrote: > On Sat, Jan 13, 2018 at 11:54 AM, Jeff King <peff@xxxxxxxx> wrote: > > I think there's also a similar feature to include timings for each fold, > > which might be worth pursuing. > > If you look for 'travis_time' in the raw log, you'll find lines like > these: > > travis_time:start:01ccbe40 > $ some-command > ... and its output ... > travis_time:end:01ccbe40:start=1515840453305552968,finish=1515840471960386859,duration=18654833891 > > So it seems doable, but we'll have to do the timekeeping ourselves. > Running 'time $cmd' is much easier, but that time won't be displayed > next to the folds, of course. > Do we really care that much? I don't care that much (and I wasn't actually planning to push the fold stuff into a patch, but would instead leave it to you people who were already working on improving the ci script output ;) ). Apparently there are exportable bash functions for all of this: http://www.garbers.co.za/2017/11/01/code-folding-and-timing-in-travis-ci/ but they're not part of the official API. So relying on them may be even more questionable than relying on the travis_fold syntax. -Peff
