https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6753
Bug #: 6753
Summary: ruleqa is handling late/early masscheck data badly
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: RuleQA
AssignedTo: [email protected]
ReportedBy: [email protected]
Classification: Unclassified
If you look at the most recent 1000 ruleqa reports, you'll see weird things
related to Axb's data:
http://ruleqa.spamassassin.org/?longdatelist=1#r20120130_r1237571_n
For the Saturday / net runs, his data doesn't show up until it's a week late,
and then it shows up with the *date* of a week later. And overwrites everybody
else's data.
Similarly, past Friday's all have their data overwritten with only Axb's data,
and with Thursday's date.
Looking at the latest masscheck net log he uploaded, I notced his "SVN
revision" line had a value that was a week old.
So I asked him if he was running masscheck too early, and it turned out he was.
So while it's (possibly?) correctable by him editing his cron job, ruleqa is
dealing with it really badly.
There was a previous bug where somebody asked how, for example, the 2012-01-21
ruleqa report could have data from a week in the future, 2012-01-28 - this is
all it takes. Grabbing the wrong SVN revision number by running masscheck too
early.
Might be useful if avoiding this problem was handled in masscheck. There's
even already dates provided with the SVN revision numbers where they come from,
weekly-versions.txt and nightly-versions.txt. They could be checked against
whatever date ends up in the right hand column of ruleqa output
("20120128-r1237024-n").
But I think the biggest problem is the overwriting.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
