-
Notifications
You must be signed in to change notification settings - Fork 121
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
[BUG] Tests do not complete successfully #347
Comments
Able to replicate locally, with additional failures on my host (Intel Mac):
|
I'm able to (successfully) build from the most recent commit, which leads me to believe this is an issue with outdated dependencies or packages. I will put together and test a new release today. |
Thanks, Paul! |
@weslambert - Release 0.23.03.14 is now available. This should work fine. In addition, #348 was created to reduce the need for users to build local images for testing. I'll add that to the documentation / README and merge in shortly. |
Great! Thanks, Paul! I agree that using the pre-built images will reduce the time to stand up the platform and likely reduce the number of issues users may run into as a result of their local configuration, or commits since the last release. |
In addition to the fix in https://github.com/target/strelka/releases/tag/0.23.03.14, prebuilt images are now available. Previously troublesome tests have also been commented out. |
Describe the bug
It appears as though the tests do not complete successfully upon installation as described by the README. This prevents starting of the services.
Environment details
Steps to reproduce
Expected behavior
Tests complete successfully and installation proceeds, or tests complete unsuccessfully and the user is provided the option to proceed anyway. Tests might not always indicate proper functioning, or may be limited to a small subset of functionality, so it would be nice to to have an option that still allows the platform to come up if tests fail.
Release
The text was updated successfully, but these errors were encountered: