I noticed that #639 was opened recently to switch from Travis CI to GitHub Actions. I can see that it's not merged and I assume it's because CI is currently failing. I've looked into it and it seems to be a series of race-conditions which means that under certain constrained environments (especially CI containers), the tests run their assertions before the tested code have completed running. This PR includes everything from #639 + a few fixes to make CI stable by increasing the test-wait-times. This is obviously not a very nice solution, but it's the solution that the current test-suite employs, so without rewriting everything, this is what I came up with.
I noticed that #639 was opened recently to switch from Travis CI to GitHub Actions. I can see that it's not merged and I assume it's because CI is currently failing. I've looked into it and it seems to be a series of race-conditions which means that under certain constrained environments (especially CI containers), the tests run their assertions before the tested code have completed running. This PR includes everything from #639 + a few fixes to make CI stable by increasing the test-wait-times. This is obviously not a very nice solution, but it's the solution that the current test-suite employs, so without rewriting everything, this is what I came up with.