From: "Alec Warner" <antarus@gentoo.org>
To: "Zac Medico" <zmedico@gentoo.org>
Cc: "Donnie Berkholz" <dberkholz@gentoo.org>,
"Mike Auty" <ikelos@gentoo.org>,
gentoo-scm@lists.gentoo.org
Subject: Re: [gentoo-scm] repoman patch for git support (from drobbins)
Date: Sun, 16 Nov 2008 13:55:59 -0800 [thread overview]
Message-ID: <b41005390811161355tc84245fy81a8228ed8a3ee92@mail.gmail.com> (raw)
In-Reply-To: <492060F5.3040206@gentoo.org>
On Sun, Nov 16, 2008 at 10:05 AM, Zac Medico <zmedico@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Alec Warner wrote:
>> [1] I fully support server-side tests but I have low expectations for
>> their implementation or deployment.
>
> Why so low? I'm pretty optimistic. ;)
Because the only person willing to work on them is you, and you are a
single point of failure; + busy.
>
>> Also it stands to reason that
>> distributed tests scale better in the long run and it is likely that
>> we could make our local tests run much faster if we dedicated some
>> developer time to it. I am sensing a possible SOC project here?
>
> The problem with running the tests locally is that our dataset is
> pretty large and the types of QA tests that it needs are pretty
> expensive. Given these constraints, it makes more sense to do the
> tests on a dedicated server than to do it on a client which may have
> limited resources.
Well if you run the expensive tests on our large datasets every time
someone commits you may soon destroy the scm server too without some
modifications, either to the tests (a daemon that caches tree state?)
or to our commit processes (pushing less often means tests run less
often means server doesn't die) or some combination of these things.
If the entire git tree is in a memory-backed FS; I'm not sure how fast
the checks are (if we eschew the memory-based daemon thing).
> - --
> Thanks,
> Zac
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
>
> iEYEARECAAYFAkkgYPMACgkQ/ejvha5XGaONpQCeJRZY1JHxreTbvQpi8R9PIlDh
> 6EYAoKEbAfmp5r5XplG1JhU+zMMK+jyp
> =R44q
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2008-11-16 21:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 1:12 [gentoo-scm] repoman patch for git support (from drobbins) Jeremy Olexa
2008-11-07 0:55 ` Robin H. Johnson
2008-11-11 10:22 ` Fabian Groffen
2008-11-11 9:36 ` Robin H. Johnson
2008-11-12 1:55 ` Zac Medico
2008-11-15 16:52 ` Mike Auty
2008-11-15 22:32 ` Zac Medico
2008-11-16 5:04 ` Donnie Berkholz
2008-11-15 22:44 ` Alec Warner
2008-11-15 23:07 ` Mike Auty
2008-11-16 4:53 ` Donnie Berkholz
2008-11-16 6:41 ` Zac Medico
2008-11-16 6:47 ` Donnie Berkholz
2008-11-16 7:10 ` Zac Medico
2008-11-16 9:34 ` Alec Warner
2008-11-16 17:20 ` Donnie Berkholz
2008-11-16 21:49 ` Alec Warner
2008-11-16 18:05 ` Zac Medico
2008-11-16 21:55 ` Alec Warner [this message]
2008-11-16 11:29 ` Mike Auty
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=b41005390811161355tc84245fy81a8228ed8a3ee92@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=dberkholz@gentoo.org \
--cc=gentoo-scm@lists.gentoo.org \
--cc=ikelos@gentoo.org \
--cc=zmedico@gentoo.org \
/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