We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
uncaughtRejection problem: it seems like we can not reject a promise twice. if so, there will be a uncaughtRejection error.
https://travis-ci.org/wechaty/wechaty/jobs/182046177#L2780
VERB StateMonitor Puppet:current(dead,true) <- (dead,false) ✔ test › puppet-web › event › Puppet Web Event smoking test (1m 31.6s) Unhandled Rejection: dist/test/puppet-web/event.spec.js WebDriverError: unknown error: Chrome failed to start: was killed (Driver info: chromedriver=2.25.426924 (649f9b868f6783ec9de71c123212b908bf3b232e),platform=Linux 4.4.0-51-generic x86_64) Object.checkLegacyResponse (/home/travis/build/wechaty/wechaty/node_modules/selenium-webdriver/lib/error.js:505:15) parseHttpResponse (/home/travis/build/wechaty/wechaty/node_modules/selenium-webdriver/lib/http.js:509:13) doSend.then.response (/home/travis/build/wechaty/wechaty/node_modules/selenium-webdriver/lib/http.js:440:13) process._tickCallback (internal/process/next_tick.js:103:7)
The text was updated successfully, but these errors were encountered:
do not reject a promise twice #122
eb8d79f
It seems reject a promise after resolve it will not cause this error.
After many days of study, I believe it's a bug inside selenium now: SeleniumHQ/selenium#3232
Sorry, something went wrong.
reject()
#122
4abd9b3
try to suppress unhandled exceptions in 3rd party library #122
da226c8
Long time no see...
No branches or pull requests
uncaughtRejection problem: it seems like we can not reject a promise twice. if so, there will be a uncaughtRejection error.https://travis-ci.org/wechaty/wechaty/jobs/182046177#L2780
The text was updated successfully, but these errors were encountered: