git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>,
	git-packagers@googlegroups.com,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Git v2.21.0-rc0 broken on *BSD, maybe others
Date: Tue, 12 Feb 2019 14:14:56 +0100	[thread overview]
Message-ID: <87pnrxjghb.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <CACsJy8D-FVGXHbqKf8BAVWEFchbF5LAN6x8UM5g7v_HLO29CLQ@mail.gmail.com>


On Tue, Feb 12 2019, Duy Nguyen wrote:

> On Tue, Feb 12, 2019 at 7:43 PM Duy Nguyen <pclouds@gmail.com> wrote:
>> The test failures on NetBSD and Solaris/Sparc, not sure if we can do
>> anything without test logs or access to these systems.
>
> Actually if you could tweak your ci script a bit to run tests with -v,
> that would help.

I vaguely remember doing that and running into some issue where it
truncated the output, so e.g. I wouldn't see compile warnings on AIX
because of the firehose of subsequent test output.

But yeah, having this in some smart way would be great. I'd be most keen
to just work towards offloading this to some smarter test runner as
noted to Johannes upthread.

I.e. a good test_for(SHA1, params) function would run the tests with
"prove", and e.g. spot that tests so-and-so failed, and then run those
specific ones with -v -x.

That's how I was going to fix the log overflow problem, but I'd much
rather not continue hacking on this gitlab-gccfarm-specific thing, and
instead work towards something more general.

  reply	other threads:[~2019-02-12 13:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07  7:28 [ANNOUNCE] Git v2.21.0-rc0 Junio C Hamano
2019-02-07 12:39 ` Christian Couder
2019-02-07 19:47 ` Johannes Schindelin
2019-02-07 19:50 ` Johannes Schindelin
2019-02-07 20:34   ` Junio C Hamano
2019-02-07 20:56     ` Junio C Hamano
2019-02-12 12:13 ` Git v2.21.0-rc0 broken on *BSD, maybe others Ævar Arnfjörð Bjarmason
2019-02-12 12:43   ` Duy Nguyen
2019-02-12 12:45     ` Duy Nguyen
2019-02-12 13:14       ` Ævar Arnfjörð Bjarmason [this message]
2019-02-12 13:16         ` Ævar Arnfjörð Bjarmason
2019-02-12 13:30         ` SZEDER Gábor
2019-02-13 14:56           ` Johannes Schindelin
2019-02-12 17:07     ` Junio C Hamano
2019-02-12 18:41       ` Junio C Hamano
2019-02-12 18:42       ` Junio C Hamano
2019-02-12 17:52     ` Junio C Hamano
2019-02-12 17:56       ` Junio C Hamano
2019-02-12 12:44   ` SZEDER Gábor
2019-02-12 13:07     ` Ævar Arnfjörð Bjarmason

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=87pnrxjghb.fsf@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git-packagers@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@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).