Tests in workflow are failing

[Falke-Design]

I don't know why but tests are often failing because the browser didn't start:

@jonkoops @mourner Can we change something to fix this? Is it possible to run the tests on the contributer repo, so they can re-start the workflow?

[johnd0e]

It's possible to re-run the test manually. At least I have enough permissions and see such button.

[Falke-Design]

Yes I know that you can do this, but others like me can't. Instead of hoping that you re-start the workflow manually, it would be good to check if we can prevent it from failing.

[johnd0e]

if we can prevent it from failing.

But we can't

[jonkoops]

Yeah, this is flaky but seems like it would be quite hard to fix, if it can really be fixed at all. We could try upping the retry count and timeout direction.

[Falke-Design]

@jonkoops I searched a little bit around and that is what I found:

Many posts are speaking of the Browser binary path is wrong, but I don't know if we have access to this: link 1, link 2

A other attempt would be to increase the timeout: doc, link 3, link 4

Or increase the retry count: doc-retryLimit

Maybe it can be fixed with: browserSocketTimeout

I reopen this, because I think we should try if we can fix it with one of the suggested ways.