On 05/18/18 00:53, John Hardin wrote:
[...]
> Yes, but that's not clear as to whether they are pulling the wrong rev or are 
> just late.
> 
>> SVN tagged rev in nightly_mass_check:  1831759
>>
>> New masscheck submission listings in the past day:
>>   1831759 (Yes) - spam-axb-ham-misc.log (May 17 11:35)
>>   1831684  (No) - ham-giovanni.log (May 17 08:38)
>>   1831684  (No) - spam-llanga.log (May 17 08:45)
> 
I takes half an hour to process my data and judging from those lines it seems 
that I am sending my data 3 hours before axb@, am I wrong ?
 

> Based on the RuleQA daterev list (at the top of the page), 1831684 *does* 
> appear to be a valid masscheck daterev (apologies for the textual 
> "screenshot"):
> 
> 
> 1831684: 2018-05-16 08:34:16
> spamassassin_role: promotions validated
> 
> 20180516-r1831684-n
> axb-coi-bulk axb-generic axb-ham-misc axb-ninja darxus ena-week0 ena-week1 
> ena-week2 ena-week3 ena-week4 giovanni jarif jbrooks llanga 
> mmiroslaw-mails-ham mmiroslaw-mails-spam sihde
> 
> 1831684: 2018-05-16 08:34:16
> spamassassin_role: promotions validated
> 
> 20180517-r1831684-n
> giovanni llanga
> 
> 1831759: 2018-05-17 08:34:10
> spamassassin_role: promotions validated
> 
> 20180517-r1831759-n (Viewing)
> axb-coi-bulk axb-generic axb-ham-misc axb-ninja darxus ena-week0 ena-week1 
> ena-week3 ena-week4 grenier jarif jbrooks mmiroslaw-mails-ham 
> mmiroslaw-mails-spam sihde thendrikx
> 
> 
> You don't see that normally because the default "last two" in the UI is 
> usually the current submissions from everybody else, preceded by the 
> apparently-late submission for the *prior* rdaterev from from giovanni and 
> llanga. You have to hit "all daterevs within 2 days" to see more history.
> 
> 
> It looks to me like their submissions are for the correct (prior) daterev 
> (SVN commit) but are coming in ~20H late... I don't think we can tweak the 
> cutoff *that* much. :)
> 
> I would be surprised if their masschecks were taking that long to complete. 
> Is it possible they have something like a TZ error causing that much of a 
> discrepancy?
> 
> 

Reply via email to