> I need some help understanding this problem now.  The "promotions
> validated" have failed for 3 weeks now so the active.list is not
> updating.  There seems to be some relationship to the masscheck ruleqa
> web output that is stuck on "day 2" failing.  See the output at the very
> bottom.

I am trying to see whats going on. I would really like some insight in the
file:
/usr/local/spamassassin/automc/html/ruleqa.cache

And i would like to have some insight into which masscheck results are
present on disk. So the output of something like this:

ls -la /usr/local/spamassassin/automc/html/2017*

ls -la /usr/local/spamassassin/automc/html/20171*/*

or something which gives me a tree view.

>
> Can someone look at the perl script "listpromotable" and figure out what
> is going on?  I can tell it's looking at the output by day to find
> "mcviewing" and "mcsubmitters".

Would you say:
http://ruleqa.spamassassin.org/?longdatelist=1
those are really all masschecks? This seems unlikely to me, I would expect
to see masschecks with many contributors much more often (every day?)


>
> This is day 1 match which is green when you view it in a browser:
>
>      <td class="daterevtd mcviewing" width='20%'>
>      <span class="daterev_masscheck_description mcviewing">
>        <p>
>          <a name="r20171106_r1814390_n"
>            href="/20171106-r1814390-n?xml=1"><strong>
>              <span class="dr">20171106-r1814390-n</span>
>            </strong></a> <b>(Viewing)</b>
>        </p><p>
>          <em><span class="mcsubmitters">axb-coi-bulk axb-generic
> axb-ham-misc darxus ena-week0 ena-week1 ena-week2 ena-week3 giovanni
> jarif jbrooks llanga mmiroslaw-mails-ham mmiroslaw-mails-spam
> thendrikx</span></em>
>          </x>
>        </p>
>
> Day 2 doesn't have that table with "mcviewing".  The next question is
> what is causing this problem.  Is it related to new commits that throw
> off the masscheck processing?

The 2 days ago doesn't highlight a current masscheck....but still it shows
a result at the bottom...so its showing *something*. I think its likely it
is the masxcheck as present in the datrev input field: 20171108-r1814560-n
But that one isn't in any daterev liting, not even in the full listing.

So i think something in the ruleqa.cgi which builds the daterev list is
broken and leaves out some masschecks.
If I get the cachefile and the ddirectory listings I can go debug where
things go pear-shaped.

>
> P.S. This cron'd script used to redirect all output to /dev/null but I
> changed it to a tee a few days ago so we could easily keep an eye on
> this output via emails to this list.
>
> Dave
>
> On 11/07/2017 02:30 AM, Cron Daemon wrote:
>> + promote_active_rules
>> + pwd
>> + /usr/bin/perl build/mkupdates/listpromotable
>> /usr/local/spamassassin/automc/svn/trunk
>> HTTP get: http://ruleqa.spamassassin.org/1-days-ago?xml=1
>> HTTP get: http://ruleqa.spamassassin.org/2-days-ago?xml=1
>> no 'mcviewing', 'mcsubmitters' microformats on day 2
>> URL: http://ruleqa.spamassassin.org/2-days-ago?xml=1
>> + exit 25
>>
>
>


Reply via email to