This test on github actions seems to fail quite regularly, giving it a
bump in how long the task that shouldn't complete 4x the amount of time
to see if this resolves the issuue (I think the github servers are just
very overloaded and a 40ms difference isn't enough to have it trigger
properly every time, lets see if 190ms is enough.)

Likely was a race condition with the stop_token being set and both tasks
returning as quickly as possible, sometimes on github this would cause
the actual task to return before the timeout job that triggered the stop
token.

Closes #355