At some point between 811de09981638e1569f45e071f4a6f3f60383234 and d310c486a49dab8cddcced90a9dc29b73701f6c4, the integration tests started taking three times as long to run. We can see this very clearly in the GitHub Actions history. We need to identify which commit caused this massive slowdown and why.
As of f1b4347, we're back to the usual time to run tests (45s on my local machine, 3.5min on GitHub Actions), so it seems #58 was the culprit after all.
At some point between 811de09981638e1569f45e071f4a6f3f60383234 and d310c486a49dab8cddcced90a9dc29b73701f6c4, the integration tests started taking three times as long to run. We can see this very clearly in the GitHub Actions history. We need to identify which commit caused this massive slowdown and why.