From: Stefan Beller <sbeller@google.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] test-lib: add ability to cap the runtime of tests
Date: Mon, 5 Jun 2017 11:56:12 -0700 [thread overview]
Message-ID: <CAGZ79kbXS83s1tizFm1y_uZZ9CYDa0zoHWH4U3HK=3-Bp5XbUg@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD3-=sDQ2PEExLq_A3v5d8w8PJ1aLgBNP725mGHzocuqqQ@mail.gmail.com>
On Sun, Jun 4, 2017 at 10:48 PM, Christian Couder
<christian.couder@gmail.com> wrote:
>> when the hidden feature is _not_ used, so that wider set of people
>> will be forced to see that some tests take inordinate amount of
>> time, and entice at least some of them to look into it.
>
> I wonder if splitting tests would make a good GSoC microproject for next year.
That is an interesting thought.
It scales pretty well IMHO.
(Have a good student that works quickly
-> we'll have very modular tests at the end,
have a student doing a-ok
-> at least parts are converted and upstreamed)
On the other hand it requires knowledge of a lot of things
(shell scripting, different operating systems come to mind..)
I like the idea.
next prev parent reply other threads:[~2017-06-05 18:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 22:13 [PATCH] test-lib: add ability to cap the runtime of tests Ævar Arnfjörð Bjarmason
2017-06-04 0:31 ` Junio C Hamano
2017-06-04 7:29 ` Ævar Arnfjörð Bjarmason
2017-06-05 1:55 ` Junio C Hamano
2017-06-05 5:48 ` Christian Couder
2017-06-05 18:56 ` Stefan Beller [this message]
2017-06-07 10:24 ` Jeff King
2017-06-08 0:59 ` Ramsay Jones
2017-06-05 13:17 ` Lars Schneider
2017-06-05 18:15 ` Ævar Arnfjörð Bjarmason
2017-06-05 19:03 ` Stefan Beller
2017-06-05 20:37 ` Æ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='CAGZ79kbXS83s1tizFm1y_uZZ9CYDa0zoHWH4U3HK=3-Bp5XbUg@mail.gmail.com' \
--to=sbeller@google.com \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).