- https://phabricator.wikimedia.org/maniphest/query/AaXo_XYy8dP0/#R
- Request: For the tasks returned that query, please (a) remove the ci-test-error (WMF-deployed Build Failure) tag, & (b) add the ci-test-error tag.
Reason: Per this clarification by @Krinkle (the third edit of the three highlighted by that link), the scope of the ci-test-error (WMF-deployed Build Failure) tag doesn't include CI failures that only occur when running check experimental (in this case, CI errors on PHP 8.4 & 8.5).
See also this discussion in #mediawiki-core on IRC:
2026-01-02 22:56:11 <A_smart_kitten> Reedy: this is probably a relatively minor point (although in any event probably good to clarify understandings), but should tasks for PHP 8.4/8.5 CI failures be tagged with the WMF-deployed build failure Phab project? 2026-01-02 22:56:28 <A_smart_kitten> just asking the understanding that i'd personally picked up over time was that the 'WMF build failure' project was for CI errors that were blocking the merging of patches in WMF-deployed repos / that were in the main/gate-and-submit tests. 2026-01-02 22:56:30 <A_smart_kitten> it's very possible that i have a mistaken understanding, though :) 2026-01-02 22:56:31 <Reedy> TBH, it's very unclear 2026-01-02 22:56:42 <Reedy> For me, if it is stuff we deploy to WMF... yes 2026-01-02 23:00:12 <Reedy> https://phabricator.wikimedia.org/project/view/4742/ 2026-01-02 23:00:18 <Reedy> >This tag is used to track issues with Jenkins jobs (in the test or gate pipeline of Zuul, or post-merge in Travis CI) that are failing due to the master branch of a WMF-deployed repository having reached a state that is not consistently passing its own tests. 2026-01-02 23:06:39 <Reedy> A_smart_kitten: and more specifically... 2026-01-02 23:06:40 <Reedy> >MediaWiki core tests failing on Travis CI for PHP versions, or database backends, not yet covered by our Jenkins jobs. 2026-01-02 23:06:56 <Reedy> I guess that travis comment is irrelevant now (let me fix it) 2026-01-02 23:09:02 <A_smart_kitten> I was gonna say, I assume it at least predates when I got more actively involved in wikimedia dev stuff :) 2026-01-02 23:11:05 <Reedy> It's been a few years since travis swapped for github actions on many repos 2026-01-02 23:12:13 <A_smart_kitten> anyhow, fair fair, that example in the Phab project description clears up the scope for me then :) mostly i just wanted to make sure i was working off the same understanding as everyone else about it 2026-01-02 23:18:21 <A_smart_kitten> the only other thing that occured to me was in case anyone wanted to track how often CI errors blocked merges in a Wikimedia-deployed repo (and wanted to use the wmf-build-failure project to do that) 2026-01-02 23:19:53 <Reedy> AFAIK we haven't tried to model that... 2026-01-02 23:20:23 <Reedy> measure 2026-01-02 23:34:49 <A_smart_kitten> fair enough 2026-01-04 06:53:15 <Krinkle> Reedy: I removed "MediaWiki core tests failing on PHP versions [..] not yet covered [..] (for example our `experimental` jobs)." because those would not be high priority to unbreak (and aren't regressions). The Travis version of that bullet point was about PHP versions that we supported and were passing but couldn't be run in Jenkins for technical reasons (eg missing packages or base images). 2026-01-04 06:54:49 <Krinkle> we track them under the PHP X.Y tags and umbrella tasks as well which seems a lot/enough. Happy to change if you think that'd be useful but afaik we haven't used it for that in recent history, and before then we didn't either for experimental / never-before-passing issues.
cc @Reedy also for info