You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2017/10/27 13:35:34 UTC
[Bug 6510] Mass-check generating nightly rules updates with 0 scores
for rules with dependencies
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6510
Merijn van den Kroonenberg <me...@web2all.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |merijn@web2all.nl
--- Comment #12 from Merijn van den Kroonenberg <me...@web2all.nl> ---
> Committed revision 1032191.
> [dos@dev new-rule-score-gen]$
>
> I've temporarily added code to force all generated scores to be non-zero and
> mark the scores-set# files to indicate that the score was changed from 0.000
> to 0.0001 with a "# forced non-zero" notation.
>
I checked svn and right after this patch was applied in
/rulesrc/sandbox/dos/new-rule-score-gen/ the scoresets had this change, so it
went live right away.
this tells us that even in nov. 2010 the
/rulesrc/sandbox/dos/new-rule-score-gen/ was used instead of
/masses/rule-update-score-gen/ which is something we (davej mostly) ran into
when reconstructing the new massgen servers.
But I am also wondering why this issue is still open? Is the behaviour still
incorrect?
>
> I've discovered that most, but not all, of the rules that have problems have
> been promoted due to "tflags publish"... which means they weren't
> necessarily selected for promotion due to mass-check results (which may
> explain their low or zero scores).
>
--
You are receiving this mail because:
You are the assignee for the bug.