From: Jonathan Nieder <jrnieder@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: gitzilla@gmail.com, Sverre Rabbelier <srabbelier@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Thomas Rast <trast@student.ethz.ch>
Subject: Re: [PATCH 2/2] t/README: Document the Smoke testing
Date: Mon, 2 Aug 2010 17:13:28 -0500 [thread overview]
Message-ID: <20100802221328.GA3826@burratino> (raw)
In-Reply-To: <AANLkTi=EuTD0M3eNo+PXW7Z2Ra2yzf-i+L4DFQVg8JZ7@mail.gmail.com>
Ævar Arnfjörð Bjarmason wrote:
> On Mon, Aug 2, 2010 at 21:04, A Large Angry SCM <gitzilla@gmail.com> wrote:
>> And what's on the site tells us almost nothing about the tested systems.
>
> Can you be more specific? What information do you find lacking at
> http://smoke.git.nix.is/app/projects/smoke_reports/1 ?
Operating system (i.e., distro). Precise CPU architecture. Number of
CPUs. Available memory. Which tests were skipped and which had expected
failures. Configuration used to build git.
(I understand that requiring all that information could prevent people
from running smoke servers, so I don’t mean to say it all should be
required.)
next prev parent reply other threads:[~2010-08-02 22:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 20:24 [PATCH 0/2] Smoke testing for Git Ævar Arnfjörð Bjarmason
2010-08-02 20:24 ` [PATCH 1/2] tests: Infrastructure for Git smoke testing Ævar Arnfjörð Bjarmason
2010-08-02 22:58 ` Avery Pennarun
2010-08-02 20:24 ` [PATCH 2/2] t/README: Document the Smoke testing Ævar Arnfjörð Bjarmason
2010-08-02 20:54 ` Sverre Rabbelier
2010-08-02 21:04 ` A Large Angry SCM
2010-08-02 22:00 ` Ævar Arnfjörð Bjarmason
2010-08-02 22:05 ` Sverre Rabbelier
2010-08-02 22:28 ` Ævar Arnfjörð Bjarmason
2010-08-02 22:13 ` Jonathan Nieder [this message]
2010-08-02 22:32 ` Ævar Arnfjörð Bjarmason
2010-08-02 22:16 ` A Large Angry SCM
2010-08-02 22:44 ` Junio C Hamano
2010-08-02 22:47 ` Sverre Rabbelier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100802221328.GA3826@burratino \
--to=jrnieder@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gitzilla@gmail.com \
--cc=srabbelier@gmail.com \
--cc=trast@student.ethz.ch \
/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.
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 NNTP newsgroup(s).