-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Hotfix for integration testing #2473
Conversation
LGTM |
1 similar comment
LGTM |
But CI failed? |
True, but I don't understand why this fails... |
@@ -3,7 +3,7 @@ RUN_MODE = prod | |||
|
|||
[database] | |||
DB_TYPE = mysql | |||
HOST = 127.0.0.1:3306 | |||
HOST = mysql:3306 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not general, just for drone. We will not be able to run tests on local env (without modifying host). Same for pgsql.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will focus on ci integration for sure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but could we run the test locally?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only if the value can be provided via some environment variable. But beside that you can also run drone exec locally.
I think we can merge this PR. Since it fix database access. For the rest, it maybe the deployment of the integration env that take to much time and is not ready for testing when it start in some conditions. |
* Hotfix for integration testing * Comment sqlite tests because of database locking issues
No description provided.