git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: larsxschneider@gmail.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH v1 2/3] travis-ci: disable verbose test output
Date: Thu, 26 May 2016 00:54:55 -0400	[thread overview]
Message-ID: <20160526045455.GD6756@sigill.intra.peff.net> (raw)
In-Reply-To: <1463914856-64745-3-git-send-email-larsxschneider@gmail.com>

On Sun, May 22, 2016 at 01:00:55PM +0200, larsxschneider@gmail.com wrote:

> From: Lars Schneider <larsxschneider@gmail.com>
> 
> The verbose output clutters the Travis CI webview and is not really
> useful since test debugging usually happens on a local machine.

I have not really been using the Travis CI results, so perhaps my
opinion does not count. But in other systems, I have found that the more
verbose the CI output, the better, simply because you will inevitably be
faced with a test that breaks on CI and not your local machine, and you
will have no way to get more details.

I don't know if Travis provides a better way to hide the output in the
non-failing cases.

-Peff

  reply	other threads:[~2016-05-26  4:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-22 11:00 [PATCH v1 0/3] travis-ci: run Git bisect on failed tests larsxschneider
2016-05-22 11:00 ` [PATCH v1 1/3] travis-ci: move "after_failure" code to dedicated file in /ci larsxschneider
2016-05-22 11:00 ` [PATCH v1 2/3] travis-ci: disable verbose test output larsxschneider
2016-05-26  4:54   ` Jeff King [this message]
2016-05-22 11:00 ` [PATCH v1 3/3] travis-ci: run Git bisect on failed tests larsxschneider
2016-05-22 15:35   ` Christian Couder
2016-05-22 16:35     ` Lars Schneider
2016-05-22 17:21   ` Pranit Bauva
2016-05-23  8:36     ` Lars Schneider
2016-05-23  1:22   ` Junio C Hamano

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=20160526045455.GD6756@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=larsxschneider@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).