This testing model deterministically scores using the last two digits of revision ID, and currently can't respond with new-style statistics, so won't work for RC filters development. Simulate statistics and include in this model.
Description
Description
Details
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Use calculated thresholds | mediawiki/vagrant | master | +8 -14 |
Related Objects
Related Objects
Event Timeline
Comment Actions
The model_info access pattern should work just fine in ORES master.
Or do you mean that we should simulate threshold statistics and store them in the revid model?
Comment Actions
That. It's constraining to not be able to test any of the thresholdy things under vagrant.
Comment Actions
While I'm being greedy, I'd like to take the dummy thresholds out of mw-vagrant and pull thresholds from the service.
Comment Actions
The ores patch is ready to go: https://github.com/wiki-ai/ores/pull/232
I'll try to integrate mw-vagrant now.
Comment Actions
Change 391578 had a related patch set uploaded (by Awight; owner: Awight):
[mediawiki/vagrant@master] Use calculated thresholds
Comment Actions
Change 391578 merged by jenkins-bot:
[mediawiki/vagrant@master] Use calculated thresholds