I'm having an Error: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test error when I try to run tests on Meteor demo app: https://github.com/meteor/todos (guide)
When I run TEST_WATCH=1 meteor test --driver-package meteortesting:mocha I get the following failed test:
17 passing (4s)
1 failing
1) todos publications todos.inList sends no todos for a private list
when not logged in:
Error: timeout of 2000ms exceeded.
Ensure the done() callback is being called in this test.
The same error happens on an app I'm developing so I can't run any integration tests.
I'm running Meteor 1.7.0.1 in the todos app and mongodb version 3.6.8, in Ubuntu 18.04.
The same project runs tests okay in my partner computers who is running the same meteor and mongodb version, but on OSX.
setting this.timeout(15000) inside tests does nothing. Also tried MOCHA_TIMEOUT environment variable with same results. Just can't modify the 2s timeout
Updated meteortesting:mocha-core to latest version and now MOCHA_TIMEOUT is being recognized, set it to 5s and now it works.
Related
The cloudrun debug in cloud shell was working. It is no longer working for me with the following output.
I have 1) rebooted the VM and 2) I have tried another project that was also working previously.
I suspect something has changed in my environment
Starting to debug the app using configuration 'Cloud Run: Run/Debug
Locally' from .vscode/launch.json... To view more detailed logs, go to
Output channel : "Cloud Run: Run/Debug Locally - Detailed" Dependency
check started Dependency check succeeded Unpausing minikube flag needs
an argument: --status-check See 'skaffold debug --help' for usage.
Exited with code 127. Cleaning up... Finished clean up.
This bug was introduced in the v1.17.1 release of Cloud Code for VS Code, due to a change in v1.37.0 of Skaffold related to the --status-check parameter. This bug was addressed in v1.17.2 of Cloud Code for VS Code, and upgrading to this version (or later) should fix this issue.
I have lately been trying to upload our UI-tests to App Center through an Azure DevOps pipeline task and seem to always run into this error. The same error also occurs if I try to run the CLI command locally. Our project is a cross platform Xamarin.Forms app using the Xamarin.UITest test framework.
The specified error:
Test chunking failed: Specified method is not supported.
Preparing tests... failed.
Error: Cannot prepare UI Test artifacts using command: C:\Users\VssAdministrator.nuget\packages\xamarin.uitest\3.0.7\tools\test-cloud.exe prepare "D:/a/1/b/Debug/Project.dev.apk" --assembly-dir "D:\a\1\s\ Project.UITest\bin\Debug" --artifacts-dir "D:\a\1\a\AppCenterTest".
Test chunking failed, please try again. If you can't work out how to fix this issue, please contact support.
##[error]Error: D:\a_tasks\AppCenterTest\1.152.3\node_modules.bin\appcenter.cmd failed with return code: 3
Any help is most appreciated.
Recently I encountered the above error (TypeError: module.exports.v1 is not a constructor) when trying to run firebase-firestore related tests. Earlier I had no issue running the tests but after doing a npm install was getting the above error.
The source of the error is from google-cloud/firestore which is required by firebase-admin.
Tried several options but it doesn't seems to get resolved. I then tried with an older node-module and it worked as expected.
The problem was due to the test framework I've been using. Once I changed from jest to mocha the problem got solved.
When I updated firebase admin sdk from 8.4.0 to higher then I had same error in running jest test code.
I fixed it to add --env node option for jest.
jest --env node
I hit this error when I left out an await on an async function. That caused my code to continue running after the jest environment had been torn down.
There was a message that said ReferenceError: You are trying to import a file after the Jest environment has been torn down. which should have been a tip that I was running async code and not waiting for completion.
We needed to upgrade node from v8.11.3 to v8.16.2.
I have deployed a Meteor app on Heroku.
I have added a platform: Android
When I try I build the app using the meteor build command meteor build --directory ~/builds --server https://my-app.herokuapp.com and the install the apk using adb, I get an error.
I get the same error when trying to run app locally, but with different server: meteor run android-device --mobile-server https://my-app.herokuapp.com
The error is:
Error: Error parsing asset manifest(…)
(anonymous function) # webapp.js?hash=2552b0d8c8f134d5763b6897c1be6c9bfa3e9c28:68
(anonymous function) # webapp_local_server.js:37
cordova.callbackFromNative # cordova.js:293
processMessage # cordova.js:1081
processMessages # cordova.js:1104
pollOnce # cordova.js:973
pollOnceFromOnlineEvent # cordova.js:960
It looks like the problem is connected to Meteor local server which runs on mobile.
Some discussion here: https://forums.meteor.com/t/meteor-local-server-on-mobile-error-error-parsing-asset-manifest/21215/7
Thanks to Meteor Forum user, issue was found.
Fixed and created a pull request for the package: https://github.com/AdmitHub/meteor-buildpack-horse/pull/86
Fresh install of Meteor 0.5.0 on Windows Vista. I don't get the basic examples working. No success after creating the empty'ish hello app either. The shell is running as admin. Meteor recognises that I changed a source file, but then nothing. It doesn't matter where in the filesystem i try this. Always getting
Exited with code: -1073741819:
eg
C:\Users\jawford\Meteor Apps\Examples>meteor create starter3
starter3: created.
To run your new app:
cd starter3
meteor
C:\Users\jawford\Meteor Apps\Examples>cd starter3
C:\Users\jawford\Meteor Apps\Examples\starter3>meteor
[[[[[ C:\Users\jawford\Meteor Apps\Examples\starter3 ]]]]]
Running on: http://localhost:3000/
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
=> Modified -- restarting.
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
^CTerminate batch job (Y/N)? y
C:\Users\jawford\Meteor Apps\Examples\starter3>
If you run into this problem using Windows 8, you will need to change compatibility mode for the node executable.
Go to the folder where you installed Meteor
Open properties for bin/node.exe
Set compatibility mode for Windows 7
You should now be able to start the application as you did earlier.
This has to do with Fibers not loading correctly. You can attempt to run app/meteor/meteor.js with bin/node, both are in the Meteor directory in Program Files. This could maybe give you more details why it is crashing. It might also be handy to run the tests in the lib/node_modules/fibers folder which might point out why Fibers is misbehaving.
The exit code -1073741819 corresponds to C0000005 which indicates an access violation.
Many users find that setting compatibility mode to "Windows 7" solves that problem, but it doesn't always and there is some evidence that it also occurs on Windows 7.
Investigating a later issue on win Meteor 0.5.9, I discovered a problem with fibers on windows that may explain this issue, and I have a tentative fix.
Please see: https://github.com/TomWij/meteor/issues/66#issuecomment-15994548 for further details.