Hi Bill, On 13.02.2026 10:57, Bill Cole wrote: > Anyone have ideas for how to fix this?
could this once again be that (my) submission time is off (though I might not be the only one) Looking at checkMasscheckContribs.sh time is 15:17 UTC > > SVN tagged rev in nightly_mass_check: 1931846 > > > > New masscheck submission listings in the past day: > > SVN rev (Match) File Name (Date) > > 1931824 (No) - ham-llanga.r1931824.log (Feb 12 17:26) but rev 1931846 was completed on my side at about Feb 13 18:34 CET (that's 17:34 UTC) so it probably means is was late at least 2 hours. yet on "in the past week" rev 1031743 seems fine at 17:25 (10 mins earlier than 13'th run. > > Recent masscheck submission listings in the past week: > > SVN rev (Match) File Name (Date) > > 1931743 (Yes) - ham-net-llanga.r1931743.log (Feb 7 17:25) I must admit never know exactly the time should run my script and to be perfectly honest ".. start your run after H hour" doesn't tell a much. The corpus is variable, the machine running the corpus also a variable and the day of the week (Sat is slower because of the -net rules). It would be much clear (at least for me) if I know the time when I have to rsync my corpus - say make sure your corpus hits the server by H hour. That way I can adapt my starting script time with the corpus size, machine and the day of the week. > See the message below. Also related errors reported to both the sysadmins and > ruleqa lists for over a week. I only got "bad performing rules" mail that doesn't tell much about submission. Can we (ruleqa) get the output of this script too and there was another (I can't remember its name) about the corpus of each contributor and the minimum threshold, that could be also useful. -- Cheers, --lucian
