-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"John Myers" writes:
> The ruleqa site isn't very forthcoming about data on the two existing 
> rules __FRAUD_DBI and INTERRUPTUS that I'm trying to get rules promoted 
> to replace.  They both show up with zero timing and hit counts.

I suspect you may have been looking at the default view -- which is the most
recent mass-check.  Since that's almost always going to be a buildbot-driven
mass-check of the sandbox rules, it won't include the core ruleset; you need to
go for a nightly mass-check to get that, via the "(List All)" link beside the
Date/Rev selection table.

(hmm, it may make more sense for the default to display the most recent
nightly mass-check, given this.)

Here's the most recent nightly:

http://buildbot.spamassassin.org/ruleqa?daterev=20051214-r356657-n&g=Change&rule=__FRAUD_DBI&s_defcorpus=on&s_detail=1&s_zero=on
http://buildbot.spamassassin.org/ruleqa?daterev=20051214-r356657-n&s_defcorpus=on&rule=INTERRUPTUS&s_zero=on&s_detail=checked+&g=Change

> Also, the rule search mechanism doesn't appear to be working.  I enter
> 
> /FRAUD_DBI/
> 
> into the "Which Rules?" field and nothing shows up.

"/FRAUD_DBI" (without quotes) is what you want, no trailing slash.
e.g.:

http://buildbot.spamassassin.org/ruleqa?daterev=20051214-r356657-n&s_defcorpus=on&rule=%2FFRAUD_DBI&s_zero=on&s_detail=checked+&g=Change

For some reason, though, that just lists __FRAUD_DBI.  It appears the
T_FRAUD_DBI sandbox rules didn't make it into that mass-check at all; I think
that may have been due to the changes I've been making to build/mkrules over
the past few days.

(The overlap data that page lists may have come from a buildbot, rather than
nightly, mass-check of the same revision, and deals with overlaps between the
T_FRAUD_DBI rules, not between them and __FRAUD_DBI.)

- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFDoz3IMJF5cimLx9ARAsRZAJ9JPXBvOwmQy/ZetFMx41p8RTWHKQCeMf8L
lnGWJjuNEikbGlLw9Pmd1Tk=
=+++J
-----END PGP SIGNATURE-----

Reply via email to