Test run flaking due to 15 minute timeout

Open Beginner friendly
#268 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, javascript, rust
Domain
ci-cd, testing

Research direction

Start with the linked GitHub Actions run and inspect the workflow timeout affecting the whole suite, then review TestToDeviceMessagesAreBatched and its Rust and JS test durations. Done means the suite no longer fails solely because it exceeds 15 minutes, confirmed by a successful workflow run.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Go
Stars
18
Forks
12
Avg merge
2d 12h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from matrix-org/complement-crypto

All issues in matrix-org/complement-crypto

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.