Open Krinkle opened 3 years ago
Nevermind. I eventually figured out that the issue was that the connection wasn't being estalished in the first place because the SAUCE_ACCESS_KEY
was missing. I mistakenly assumed that GitHub Actions would work similarly to Travis CI and allow forked repositories to provide their own secrets. But, despite GitHub happily allowing you to configure secrets in a forked repo, these are completely ignored.
It might be good if karma-sauce-launcher would give a better error message since there is nothing in the above that suggests incorrect or missing credentials, or indeed anything about the connection not being established.
The two errors shown are both "wrong", there is no 60s timeout reached, and there is no issue in quiting the connection. There was never a connection in the first place.
If that's a valid issue and not an upstream issue, great. Otherwise, feel free to close this :)
I want to work on this issue as I am new so please guide me through.
Environment:
Example at https://github.com/Krinkle/kiwix-js/runs/1620210786?check_suite_focus=true
It works fine from my machine with Node.js 10.15.2 on Debian 9 Stretch (via Docker for Mac), and it used to work fine on Travis CI, but now on GitHub Actions I can't get it work.
I've tried everything I could think of, including different Node.js versions and the latest versions of dependencies, and verifying that credentials are making it through.
As you can see from the timestamps, it happens immediately upon startup, so contrary to the warning, it is not a timeout. (The error message itself might be a secondary problem, as that led to some additional confusion initially.)