From: Jeff King <peff@peff.net>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Lars Schneider <larsxschneider@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Git mailing list <git@vger.kernel.org>
Subject: Re: [PATCH] travis-ci: build Git during the 'script' phase
Date: Sun, 14 Jan 2018 06:10:48 -0500 [thread overview]
Message-ID: <20180114111048.GB13643@sigill.intra.peff.net> (raw)
In-Reply-To: <CAM0VKjkmEThnM7KdQ=SJFGK1E_zdjsCFnFas7fsRG97aQmS52g@mail.gmail.com>
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@peff.net> 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
next prev parent reply other threads:[~2018-01-14 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 17:22 [PATCH] travis-ci: build Git during the 'script' phase SZEDER Gábor
2018-01-08 22:07 ` Junio C Hamano
2018-01-08 22:38 ` Lars Schneider
2018-01-12 13:32 ` SZEDER Gábor
2018-01-13 10:32 ` Jeff King
2018-01-13 10:54 ` Jeff King
2018-01-14 10:43 ` SZEDER Gábor
2018-01-14 11:10 ` Jeff King [this message]
2018-01-14 10:37 ` SZEDER Gábor
2018-01-14 11:07 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180114111048.GB13643@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
--cc=szeder.dev@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).