If the whole test suite takes longer than 15 minutes, it will time out.
https://github.com/matrix-org/complement-crypto/actions/runs/30901217236/job/91965706809?pr=263 is an example of such. The whole thing is quite slow, but a lot of the problem is TestToDeviceMessagesAreBatched which took over 5 minutes, between the Rust and JS tests. That said, even on a good run, that test takes 2 minutes.
I guess we just had a slow actions runner. We might want to consider bumping the timeout.
If the whole test suite takes longer than 15 minutes, it will time out.
https://github.com/matrix-org/complement-crypto/actions/runs/30901217236/job/91965706809?pr=263 is an example of such. The whole thing is quite slow, but a lot of the problem is
TestToDeviceMessagesAreBatchedwhich took over 5 minutes, between the Rust and JS tests. That said, even on a good run, that test takes 2 minutes.I guess we just had a slow actions runner. We might want to consider bumping the timeout.