One shard on the daily test workflow is taking 20 minutes to complete

[AlexWaygood]

One of these things is not like the others:

Screenshot

None of the other shards take more than 6 minutes.

Link to workflow run: https://github.com/python/typeshed/actions/runs/13021949798

[AlexWaygood]

Four days ago the workflow was still completing in <9 minutes: https://github.com/python/typeshed/actions/runs/12969611420

[AlexWaygood]

It looks like it's taking a very long time to run stubtest on google-cloud-ndb

[AlexWaygood]

It's unclear what's changed. The last release of google-cloud-ndb was in September.

[srittau]

For reference, here we can see that the google-cloud-ndb tests run for 903.70 s aka 15 min: https://github.com/python/typeshed/actions/runs/13555948200/job/37890157810. I can reproduce this locally.

Another check from the same shard that takes surprisingly long is the ldap3 check, which takes about a minute, with most checks lasting well below 10s. I suspect some stubtest shenanigans, which warrants a closer inspection.

[srittau]

I wrongly blamed stubtest. At least for google-cloud-ndb and dateparser installing the dependencies is what takes so long. Locally, for google-cloud-ndb pip installing google-cloud-ndb[]==2.3.* mypy==1.15.0 protobuf==3.20.2 six took 433 seconds (> 7 minutes), while running stubtest only took a good second. Installing the dependencies for dateparser took ~20s, probably because numpy is among the indirect dependencies.

[srittau]

In the case of google-cloud-ndb, the ancient stubtest requirements (that are unnecessary by now) cause pip to download many different versions of the various indirect dependencies, trying to find a solution. It eventually succeeds, but needed to download all of PyPI for it.