In T248779#7087130, @Krinkle wrote:

20min instead of 22min. Not as much as I'd hoped, but also not that surprising given most steps are serial. It does eliminate one difference with GitHub Actions (which provides 2 cores).

First "success"
https://integration.wikimedia.org/ci/job/mw-cli-test/24/consoleFull
With https://gerrit.wikimedia.org/r/690012 applied, more disk space in the image and a 60 min timeout
The test took 10 mins to install dependencies (docker-compose, go etc), 1 min to build the binary, 1 min to clone core, 10 mins to run the start command (which includes pulling docker images), 7 mins to install composer dependencies, 2 mins to run the rest of the tests?

I tweaked the test so that we can see the output of the start command (as before it was just being assigned to a var)
https://gerrit.wikimedia.org/r/c/mediawiki/tools/cli/+/690012/5..6/test

I re ran the job now using the newer image.
It no longer complains about running out of disk space, but it does just unhelpfully timeout

Specially picking from https://integration.wikimedia.org/ci/job/wmf-quibble-selenium-php72-docker/94431/consoleFull

IMO this probably relates to T281122: Wikibase selenium tests timeout, seemingly due to "memory compaction" events on CI VMs in general if we are talking about browser tests being slow.

Reading guides etc I think I managed to figure out the process for resizing

@jeena and I were doing some debugging to get this working in https://gerrit.wikimedia.org/r/c/mediawiki/tools/cli/+/690012 which included things like seting up .env but also installing docker-compose.

Looks good to me!
https://codesearch.wmcloud.org/extensions/?q=SkinTemplateNavigation&i=nope&files=&excludeFiles=&repos=Extension:Wikibase

Looks good to me!

Woo!

Looking good!
https://codesearch.wmcloud.org/deployed/?q=(mw-ajax-loader%7Cmw-small-spinner)&i=nope&files=&excludeFiles=&repos=mediawiki/extensions/Wikibase

@CCicalese_WMF named this as one of the more important currently missing things.

In T274506#6847803, @Lucas_Werkmeister_WMDE wrote:

I think this is the same issue as T144248: No RDF builder defined for data type globe-coordinate nor for value type bad in DispatchingValueSnakRdfBuilder::getValueBuilder – in the JSON representation I see:

$ curl -s https://www.wikidata.org/wiki/Special:EntityData/Q3642430.json | jq .entities.Q3642430.claims.P625[0].mainsnak
{
  "snaktype": "value",
  "property": "P625",
  "datavalue": {
    "value": {
      "latitude": 90,
      "longitude": 0,
      "altitude": null,
      "precision": 146706019195900,
      "globe": "http://www.wikidata.org/entity/Q308"
    },
    "type": "globecoordinate",
    "error": "$precision needs to be between -360 and 360"
  },
  "datatype": "globe-coordinate"
}

From the other ticket I merged in:

@hashar Do you see any more occurrences of this in logstash?
I couldn't find any, or the original.
This is perhaps fixed by T157868: Lua functions do not resolve redirects

I have split the last reported occurrence into T282534: Unresolved redirect in Wikibase LUA code, in v3/page/pagebundle
This ticket has become a bit of a kitchen sink,. so closing it and will track this last occurrence there.

In T228293#7077419, @Michael wrote:

Occurences of UnresolvedEntityRedirectException in the last 90 days:

from: https://logstash.wikimedia.org/goto/887045bfef70f63d31994d8b04b8d6ff

The lexeme tests seem to be green now, although there is another issue causing failure now

Force re running right now to see if this is green
https://integration.wikimedia.org/ci/job/selenium-daily-beta-WikibaseLexeme/1010/

codesearch says this looks good

Looks pretty good, thanks for spotting the other task too!

@Lydia_Pintscher we don't have ACs for this one, but we should probably update the docs too?

Looks good.
The code for LIBXML_NOBLANKS was in https://github.com/wmde/php-vuejs-templating/commit/fa76a8bd09adec03c837a428c04e49ec55cb657d

Jakon on mattermost:

Just looked again and we are at a pretty low point in terms of errors right now :)

More work in progress was pasted at P15869