Testing process on SauceLabs doesn't complete properly

[Aaronius]

When tests are running on SauceLabs, the process fails. Here's the last relevant message:

09 05 2020 16:58:47.168:WARN [launcher]: Chrome on SauceLabs have not captured in 60000 ms, killing.

See an example failed build here: https://travis-ci.org/github/Aaronius/penpal/builds/685098099

I've tried several configuration changes but haven't had success fixing the problem. Alternatively, explore different testing solutions entirely.

[celesterobinson]

One option would be to ditch TravisCI and use the Sauce Labs CLI in conjunction with GitHub actions.

I'm happy to submit a PR with the workflow, then you can add your Sauce Labs credentials to a GitHub secret.

[Aaronius]

Let's do it!

[celesterobinson]

Before completely throwing out TravisCI, I'm curious what configuration changes you tried. Did you try launching chrome with no sandbox?

[Aaronius]

It's been a few years, so I don't even remember at this point. I believe it was before Github Actions were a thing. I'd rather just use Github Actions at this point.

[celesterobinson]

Could you give me permissions to edit actions on the repo while I work on this? I'm not sure which permission it is, but I currently can't re-run jobs :(

[Aaronius]

I tweaked a permission. See if that works. If it doesn't, I'll need to do some more research.

[Aaronius]

Are you able to re-run jobs now @celesterobinson?

[celesterobinson]

Yes! Much thanks. I haven't had time for a while to look at this but I'll have a lot of time next week.

[celesterobinson]

@Aaronius I'm not sure if they're already set up, but would you mind setting up the repo secrets?
Keys:
SAUCE_USERNAME
SAUCE_ACCESS_KEY

I realized I need them in there to test the workflow

[Aaronius]

Okay, the secrets are set!

[Aaronius]

I'm also good with going with BrowserStack if SauceLabs gives us trouble. I've had better luck with BrowserStack in other projects.

[Aaronius]

If someone picks this up, let's move to BrowserStack.