it is nice to have a higher threshold for daily comments from orangefactor, but for the weekly comments it is good to have a sense if we are getting periodic failures. Specifically if we want to close out bugs that have no activity for 3 weeks, it requires querying orangefactor. This should be possible in this code: https://hg.mozilla.org/automation/orangefactor/file/tip/woo_commenter.py#l26 by changing: WEEKLY_THRESHOLD=5 to be: WEEKLY_THRESHOLD=1

Comment on attachment 8877542 [details] [diff] [review] adjust weekly threshold from 5->1 I'm fine with this - I'll leave it up to you whether further discussion might be required with sheriffs or devs :-) (Once I see the commit URL in the bug for this landing, I'll deploy)

Deployed: [webtools@brasstacks1.dmz.scl3 ~]$ cd ~/apps/orangefactor/src/orangefactor/ && hg pull -uv pulling from https://hg.mozilla.org/automation/orangefactor/ warning: hg.mozilla.org certificate with fingerprint 73:7f:ef:ab:68:0f:49:3f:88:91:f0:b7:06:69:fd:8f:f2:55:c9:56 not verified (check hostfingerprints or web.cacerts config setting) searching for changes all local heads known remotely adding changesets adding manifests adding file changes added 6 changesets with 10 changes to 6 files resolving manifests getting deployment/locations getting deployment/openidc_config.lua-example getting deployment/openidc_layer.lua getting deployment/orangefactor.conf getting server/handlers.py getting woo_commenter.py 6 files updated, 0 files merged, 0 files removed, 0 files unresolved