-
Notifications
You must be signed in to change notification settings - Fork 23
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
Integration tests fail (in GOV.UK Docker) #210
Comments
Note that the router build with GOV.UK Docker has been broken for other reasons, as well, so you may need to pull the latest version after the final fix has been added: alphagov/govuk-docker#489. |
Dup of alphagov/govuk-docker#591. It doesn't look like anyone's actually needed to run Router in govuk-docker in the past 3 years or so. We hope to start replacing govuk-docker use cases with Kubernetes soon, so it'll become possible to run end-to-end tests locally. |
This regression was introduced in: 678ef63
It looks like the new code requires the Mongo DB to be a replica set. The test failures don't give any insight into the cause of the error, probably because the router is being run as a separate binary, and doesn't seem to be logging its errors anywhere.
Example failure:
List of more failures:
I get a more informative error if I start the app manually:
I tried to fix this manually in GOV.UK Docker, and while the app started without errors, the integration tests are still failing for some unknown reason, due to the logs being mysteriously absent.
I think this is equally an issue for anywhere trying to develop this repo without GOV.UK Docker, since the README doesn't provide any specialist instructions about installing or configuring MongoDB.
I'd say this issue is resolved when:
We can see error logs from the router when we run integration tests. It may be these are being output somewhere; we could document where they're going, or change the file path so it's more obvious.
I can run integration tests in GOV.UK Docker and they pass, with the reasonable exception of the performance tests.
The text was updated successfully, but these errors were encountered: