Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bury to Spydus; Luci tests require VPN #36

Merged
merged 5 commits into from
Apr 8, 2023

Conversation

cpwood
Copy link
Contributor

@cpwood cpwood commented Mar 25, 2023

Bury

Has moved to Spydus. data.json updated and test passes.

Test automation and Luci

The problem

We've hit a bit of a problem with the tests for Luci. They've failed the last two weeks but worked fine on my computer. My theory was that connections from outside the UK are being blocked by their servers, and I've now confirmed that by trying to run the tests when connected to a VPN to the US.

It's not possible to choose a region to run a GitHub Action in. All GitHub's servers are in the US.

Updates to the Action

I've updated the YAML file for the GitHub action so it launches an OpenVPN connection to a server prior to the tests running. The URL for the connection profile, the username and the password can be stored as secrets in the repository's configuration. For my fork of the repo, I'm using my Express VPN credentials to access their UK server prior to running the tests. The Luci tests do now pass.

Ways forward

Unfortunately, this has added a bit of complexity to something that really ought to be far more straightforward!

Since I'd rather not share my ExpressVPN credentials (sorry!), I guess there are the following ways forward:

  1. You could disable the Action in the LibrariesHacked and I'll just keep it running in my fork. I'll continue to do fixes as and when required.
  2. You could use your own connection profile, username and password in the LibrariesHacked origin.

Also open to other ideas..!

@DaveBathnes DaveBathnes merged commit 484ddba into LibrariesHacked:main Apr 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants