-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Issues with Weather Tests. - Tests currently disabled. #1840
Comments
After merge #1849 I could check it |
Fixed by reverting electron. See #1800 |
still failing today |
They run ok now. They timeout after 10sec. We might need to stretch that 10 sec. |
The code says if under CI then timeout is 30 seconds |
This line (for example) uses 10000ms: |
Ok. Other tests call a function in global_setup to set timeouts. Figured they all would |
I've try catch the failed of this and apparently is because is too slow to run these tests. There a other line |
@roramirez @MichMich I tried this morning the newest version of develop and run the tests locally, they all passed after ~7s. What is the setup I need to reproduce the issue? Since this seems to be still relevant, we should reopen the issue. |
Hi @fewieden You should try into a similar environment where is running like Travis. Maybe you can using the follow guide (I'm use this one) https://jonlabelle.com/snippets/view/markdown/run-travis-ci-builds-locally-with-docker. Or also requests the debug mode for your Fork in Travis
Yes. Should reopen this issue |
@roramirez the PR that you tried to reference is a link to this issue. Therefore I tried https://jonlabelle.com/snippets/view/markdown/run-travis-ci-builds-locally-with-docker to debug this commit which had the original build log. Executing the tests inside the docker container resulted in a different error What I found is https://stackoverflow.com/questions/50642308/webdriverexception-unknown-error-devtoolsactiveport-file-doesnt-exist-while-t but even with adding all those argumens to the chrome driver the issue still appeared. Maybe I passed them wrong? Running the tests locally gives a third result. Sometimes they pass, sometimes the same tests fail. I could see that they made actual requests to the api server instead of using the mock. Maybe we have a timing iue in there. Updating electron and spectron to their latest stable versions is passing all the tests. What is failing, is the npm list command afterwards. CC @MichMich |
Hi @fewieden You're right. I've reference wrong the PR. This should be #1892. Sorry for that. This change is already merge in The problem you are getting is because the sandbox mode is enable by default. More information about this is #1892 Setting the enviroment variable |
@roramirez looks like I found the issue |
Merged! |
For some unknown reason most of the weather module tests seem to fail (both on Travis as well as local) due to timeout issues. To be able to continue the development I have disabled the weather tests by adding a skip statement: https://github.com/MichMich/MagicMirror/blob/develop/tests/e2e/modules/weather_spec.js#L18
This means the weather tests are currently not used. This could impact the quality of the code. I can't seem to find any reason why these tests time out.
If anyone is able to solve this issue and get travis to successfully complete the tests, please send a PR. Your contribution would be highly appreciated.
Thanks!
The text was updated successfully, but these errors were encountered: