Thanks. Just to clarify, I am not changing --fuzz. I am testing --ktf-to-fail in
conjunction with other parserTests options to ensure there is no interference. The chances
of such interference is very small, but since I have been preaching the importance of
regression testing, I thought I should eat my own dog-food.
--- On Wed, 7/22/09, Tim Starling <tstarling(a)wikimedia.org> wrote:
From: Tim Starling <tstarling(a)wikimedia.org>
Subject: Re: [Wikitech-l] Known to fail interactions with compare and record
To: wikitech-l(a)lists.wikimedia.org
Date: Wednesday, July 22, 2009, 10:17 PM
dan nessett wrote:
Well, it isn't all that clear to me, but I
really
don't care. I'll
change it to whatever people want. "Call me
anything
you like, but
don't call me late for dinner."
Can someone tell me how the --fuzz option is supposed
to behave? I
am cross-testing the new parserTests parameter in
conjunction with
its other parameters. I have tested --quick and
--quiet. They seem
to work fine with ktf-to-fail. When I test
--fuzz,
parserTests
seems to go on walkabout in the Great Australian
desert
periodically spewing out stuff like:
100: 100/100 (mem: 36%) 200: 200/200 (mem: 37%) 300:
300/300 (mem:
37%) 400: 400/400 (mem: 37%) 500: 500/500 (mem:
38%)
600: 600/600
(mem: 38%) ....
Is this expected behavior? Is parserTests supposed to
finish when
you use --fuzz or is this some kind of stress
test
that the never
finishes?
It runs forever, unless it runs out of memory or hits a
fatal PHP
error. It's not a stress test, it's a fuzz test, hence the
name. It
logs exceptions generated by the parser for random input.
Maybe if there's an undocumented option that you don't
understand, you
should leave it alone. Otherwise some day your wiki will
end up with
all its articles deleted, or with all the text converted
to
ISO-2022-JP or something.
-- Tim Starling
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l