From: Thomas Zander <TZander@factotummedia.nl>
To: Jeroen Frijters <jeroen@sumatra.nl>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Unicode test noise
Date: Mon, 31 Jan 2005 12:32:00 -0000 [thread overview]
Message-ID: <20050131123159.GA1875@factotummedia.nl> (raw)
In-Reply-To: <D92197D0A6547B44A1567814F851FA68069405@LEMBU.sumatrasoftware.com>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
But it really is a lot of tests; there is nothing wrong with that.
The real fix is in a better runner. Perhaps I should publish the runner I
have been working on, it solves this problem already. (except that you
get one page which is really big :)
I think any of those changes are not a good idea.
On Mon, Jan 31, 2005 at 01:13:58PM +0100, Jeroen Frijters wrote:
> Michael Koch wrote:
> > Am Montag, 31. Januar 2005 12:34 schrieb Jeroen Frijters:
> > > Hi,
> > >
> > > Does anyone have any objections against this patch to eliminate the
> > > noise that the unicode test generates?
> >
> > Why don't you just skip the tests ? You change would make the tests
> > don't show up in summaries when they succeed.
>
> I don't want to skip the tests, it's just that I don't think it is
> meaningful to have that single test count as 3.5 million tests, and in
> addition it makes the -verbose option incredibly slow.
>
> How about this patch?
>
> Regards,
> Jeroen
--
Thomas Zander
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-31 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 12:14 Jeroen Frijters
2005-01-31 12:32 ` Thomas Zander [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-31 11:35 Jeroen Frijters
2005-01-31 11:41 ` Michael Koch
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=20050131123159.GA1875@factotummedia.nl \
--to=tzander@factotummedia.nl \
--cc=jeroen@sumatra.nl \
--cc=mauve-discuss@sources.redhat.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.
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).