https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6821
Priority: P2
Bug ID: 6821
Assignee: [email protected]
Summary: Masscheck is not including logs for everyone who is
uploading
Severity: normal
Classification: Unclassified
OS: Windows 7
Reporter: [email protected]
Hardware: PC
Status: NEW
Version: SVN Trunk (Latest Devel Version)
Component: Building & Packaging
Product: Spamassassin
At a minimum, there appear to be issues with some log files not being included
in the masscheck analysis. Jari and Kevin Golding, for example.
There does not appear to be an upload problem.
If I look at the server, I see Jari's files and Kevin Golding's.
However, I believe when I see: axb-coi-bulk axb-fraud axb-generic axb-sa-users
axb-woas bb-guenther_fraud bb-jhardin bb-jhardin_fraud bb-jm bernie-fsf
bernie-it_batt bernie-mix danmcdonald darxus grenier on the list of.
That shows that Jari's uploads, for example, are not being used. Correct?
I'm trying to see if I have any logs that show Jari vs. Axb upload file.
Ok, going through cron, I see this which is good:
Your "cron" job on spamassassin.zones.apache.org
bash
/export/home/updatesd/svn/mkupdates-with-scores/do-stable-update-with-scores
produced the following output:
Running do-nightly-rescore-example...
At revision 1370633.
Wed Aug 8 02:25:01 GMT 2012
[ rsyncing logs locally ]
building file list ... done
ham-axb-coi-bulk.log
ham-axb-fraud.log
ham-axb-generic.log
ham-axb-sa-users.log
ham-axb-woas.log
ham-bb-guenther_fraud.log
ham-bb-jhardin.log
ham-bb-jhardin_fraud.log
ham-bb-jm.log
ham-bernie-fsf.log
ham-bernie-it_batt.log
ham-bernie-mix.log
ham-danmcdonald.log
ham-darxus.log
ham-grenier.log
ham-jarif.log
ham-kgolding.log
ham-llanga.log
spam-axb-coi-bulk.log
spam-axb-fraud.log
spam-axb-generic.log
spam-axb-sa-users.log
spam-axb-woas.log
spam-bb-guenther_fraud.log
spam-bb-jhardin.log
spam-bb-jhardin_fraud.log
spam-bb-jm.log
spam-bernie-fsf.log
spam-bernie-it_batt.log
spam-bernie-mix.log
spam-danmcdonald.log
spam-darxus.log
spam-grenier.log
spam-jarif.log
spam-kgolding.log
spam-llanga.log
sent 838170324 bytes received 740 bytes 42983131.49 bytes/sec
total size is 6085599473 speedup is 7.26
but I don't really ever see any more information that let's me deduce what
files are being used.
I believe
/export/home/updatesd/svn/mkupdates-with-scores/do-stable-update-with-scores
and all the scripts it calls are in need of some debug statements.
I'm going to start with generate-new-scores.
I'm adding this:
svn diff
Index: generate-new-scores
===================================================================
--- generate-new-scores (revision 1353252)
+++ generate-new-scores (working copy)
@@ -59,24 +59,28 @@
do
FILE=`echo $FILE | cut -d"/" -f2-`
ln corpus/$FILE corpus/usable-corpus-set${SCORESET}/$FILE || exit $?
+ echo "Linked $FILE to corpus/usable-corpus-set${SCORESET}/$FILE"
done
elif [ $SCORESET -eq 2 ]; then
for FILE in `find corpus -type f -name "*am-bayes-*" | grep -v net-`;
do
FILE=`echo $FILE | cut -d"/" -f2-`
ln corpus/$FILE corpus/usable-corpus-set${SCORESET}/$FILE || exit $?
+ echo "Linked $FILE to corpus/usable-corpus-set${SCORESET}/$FILE"
done
elif [ $SCORESET -eq 1 ]; then
for FILE in `find corpus -type f -name "*am-net-*"`;
do
FILE=`echo $FILE | cut -d"/" -f2-`
ln corpus/$FILE corpus/usable-corpus-set${SCORESET}/$FILE || exit $?
+ echo "Linked $FILE to corpus/usable-corpus-set${SCORESET}/$FILE"
done
elif [ $SCORESET -eq 0 ]; then
for FILE in `find corpus -type f -name "*am-*" | grep -v net- | grep -v
bayes-`;
do
FILE=`echo $FILE | cut -d"/" -f2-`
ln corpus/$FILE corpus/usable-corpus-set${SCORESET}/$FILE || exit $?
+ echo "Linked $FILE to corpus/usable-corpus-set${SCORESET}/$FILE"
done
else
echo "Unknown score set: $SCORESET"
@@ -94,7 +98,8 @@
for FILE in `find corpus/usable-corpus-set$SCORESET -type f`;
do
- head $FILE | grep "SVN revision: $REVISION" || rm $FILE
+ echo "Checking $FILE for SVN $REVISION..."
+ head $FILE | grep "SVN revision: $REVISION" || (rm $FILE; echo "$FILE does
not meet the requirements")
done
date
Hopefully, this will show more information when cron fires off next.
--
You are receiving this mail because:
You are the assignee for the bug.
