[01:59:09] PROBLEM - puppet on ORES-web01.Experimental is UNKNOWN: UNKNOWN: Failed to check. Reason is: failed_to_parse_summary_file [02:31:49] PROBLEM - puppet on ORES-worker01.experimental is UNKNOWN: UNKNOWN: Failed to check. Reason is: failed_to_parse_summary_file [02:51:12] PROBLEM - puppet on ORES-web02.Experimental is UNKNOWN: UNKNOWN: Failed to check. Reason is: failed_to_parse_summary_file [02:58:02] RECOVERY - puppet on ORES-web01.Experimental is OK: OK: Puppet is currently enabled, last run 4 minutes ago with 0 failures [03:00:44] PROBLEM - puppet on ORES-worker01.experimental is WARNING: Could not resolve hostname ores-worker-01.ores.eqiad.wmflabs: Name or service not known [03:05:32] PROBLEM - puppet on ORES-worker01.experimental is UNKNOWN: UNKNOWN: Failed to check. Reason is: failed_to_parse_summary_file [03:29:49] RECOVERY - puppet on ORES-worker01.experimental is OK: OK: Puppet is currently enabled, last run 3 minutes ago with 0 failures [03:45:38] RECOVERY - puppet on ORES-web02.Experimental is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures [03:50:54] PROBLEM - puppet on ORES-worker02.experimental is UNKNOWN: UNKNOWN: Failed to check. Reason is: failed_to_parse_summary_file [04:15:22] RECOVERY - puppet on ORES-worker02.experimental is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [06:31:11] PROBLEM - check load on ORES-web02.Experimental is CRITICAL: connect to address 172.16.6.234 port 5666: Connection refusedconnect to host ores-web-02.ores.eqiad.wmflabs port 5666: Connection refused [06:31:12] PROBLEM - puppet on ORES-web02.Experimental is CRITICAL: connect to address 172.16.6.234 port 5666: Connection refusedconnect to host ores-web-02.ores.eqiad.wmflabs port 5666: Connection refused [06:31:47] PROBLEM - check disk on ORES-web02.Experimental is CRITICAL: connect to address 172.16.6.234 port 5666: Connection refusedconnect to host ores-web-02.ores.eqiad.wmflabs port 5666: Connection refused [06:31:52] PROBLEM - check users on ORES-web02.Experimental is CRITICAL: connect to address 172.16.6.234 port 5666: Connection refusedconnect to host ores-web-02.ores.eqiad.wmflabs port 5666: Connection refused [06:35:25] PROBLEM - check load on ORES-web01.Experimental is CRITICAL: connect to address 172.16.3.131 port 5666: Connection refusedconnect to host ores-web-01.ores.eqiad.wmflabs port 5666: Connection refused [06:35:41] PROBLEM - check users on ORES-web01.Experimental is CRITICAL: connect to address 172.16.3.131 port 5666: Connection refusedconnect to host ores-web-01.ores.eqiad.wmflabs port 5666: Connection refused [06:36:11] PROBLEM - check disk on ORES-web01.Experimental is CRITICAL: connect to address 172.16.3.131 port 5666: Connection refusedconnect to host ores-web-01.ores.eqiad.wmflabs port 5666: Connection refused [06:39:09] PROBLEM - puppet on ORES-web01.Experimental is CRITICAL: connect to address 172.16.3.131 port 5666: Connection refusedconnect to host ores-web-01.ores.eqiad.wmflabs port 5666: Connection refused [07:15:43] RECOVERY - puppet on ORES-web02.Experimental is OK: OK: Puppet is currently enabled, last run 9 seconds ago with 0 failures [07:15:47] RECOVERY - check disk on ORES-web02.Experimental is OK: DISK OK [07:15:52] RECOVERY - check users on ORES-web02.Experimental is OK: USERS OK - 1 users currently logged in [07:17:11] RECOVERY - check load on ORES-web02.Experimental is OK: OK - load average: 0.17, 0.12, 0.13 [07:23:16] RECOVERY - puppet on ORES-web01.Experimental is OK: OK: Puppet is currently enabled, last run 36 seconds ago with 0 failures [07:23:21] RECOVERY - check users on ORES-web01.Experimental is OK: USERS OK - 1 users currently logged in [07:23:25] RECOVERY - check load on ORES-web01.Experimental is OK: OK - load average: 0.20, 0.17, 0.22 [07:24:11] RECOVERY - check disk on ORES-web01.Experimental is OK: DISK OK [14:34:14] so I tried to make same stats on anon edit usefulness in huwiki with the dataset from T223900 [14:34:15] T223900: Create ORES dataset for huwiki edits in the last two years or so - https://phabricator.wikimedia.org/T223900 [14:35:15] my naive attempt was to count the number of edits where the ORES damaging score is > 0.1 [14:35:40] turns out that's every anon edit, ever [14:35:55] (okay, not literally, but over 99.9% of anon edits) [14:36:14] empirically, about a third of anon edits seem bad [14:36:47] so now I'm wondering, is that a really poor choice of cutoff, or is the classifier horribly biased against anons? [14:37:33] I did expect bias, but not that much [14:37:34] (this is pre-T228078 data, FWIW) [14:37:36] T228078: Retrain damaging/goodfaith models for huwiki - https://phabricator.wikimedia.org/T228078 [14:39:06] if I'm being too conservative with the cutoff, what would be a reasonable choice? [15:19:06] at a cutoff of .5 it still considers 80% of anon edits damaging [15:25:50] 10Scoring-platform-team (Current), 10Wikilabels, 10editquality-modeling, 10artificial-intelligence: Re-label huwiki damaging and badfaith edits - https://phabricator.wikimedia.org/T223882 (10Bencemac) Are there any new information/update? [18:07:36] 10Jade, 10ci-test-error: Unit tests of Jade extensions failing - https://phabricator.wikimedia.org/T215459 (10Umherirrender)