Title: Runner exits with failures while browser tests report none · Issue #201 · browserstack/browserstack-runner · GitHub
Open Graph Title: Runner exits with failures while browser tests report none · Issue #201 · browserstack/browserstack-runner
X Title: Runner exits with failures while browser tests report none · Issue #201 · browserstack/browserstack-runner
Description: Bug For unknown reasons, browserstack-runner sometimes exits with failures while all tests run without errors. For exemple see the following Travis job with mocha: all tests passed (or are skipped) but browserstack-runner exists with fai...
Open Graph Description: Bug For unknown reasons, browserstack-runner sometimes exits with failures while all tests run without errors. For exemple see the following Travis job with mocha: all tests passed (or are skipped)...
X Description: Bug For unknown reasons, browserstack-runner sometimes exits with failures while all tests run without errors. For exemple see the following Travis job with mocha: all tests passed (or are skipped)...
Opengraph URL: https://github.com/browserstack/browserstack-runner/issues/201
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Runner exits with failures while browser tests report none","articleBody":"### Bug\r\n\r\nFor unknown reasons, `browserstack-runner` sometimes exits with failures while all tests run without errors.\r\n\r\nFor exemple see the following Travis job with `mocha`: all tests passed (or are skipped) but `browserstack-runner` exists with `failures: 3`.\r\n```log\r\nUsing config: /home/travis/build/ncoden/foundation-sites/browserstack.json\r\nLaunching 18 worker(s) for 18 run(s).\r\n[OS X Sierra, Safari 10.1] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 6546ms\r\n[Windows 10, Internet Explorer 11.0] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 14034ms\r\n[Windows 8, Chrome 65.0] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 6260ms\r\n[Windows 10, Chrome 66.0] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 7288ms\r\n[Windows 7, Internet Explorer 10.0] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 15411ms\r\n[Windows 10, Internet Explorer 11.0] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 16303ms\r\n[Windows 8.1, Firefox 60.0] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 10193ms\r\n[Windows 7, Opera 53.0] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 5517ms\r\n[ios 7.0, Mobile Safari null] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 18048ms\r\n[Windows 10, Edge 17.0] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 9909ms\r\n[Windows 7, Opera 52.0] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 5855ms\r\n[OS X High Sierra, Safari 11.1] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 9277ms\r\n[Windows 10, Firefox 61.0 beta] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 10925ms\r\n[Windows 10, Edge 16.0] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 11188ms\r\n[android 8.0, Android Browser null] Passed: 260 tests, 252 passed, 0 failed, 8 skipped; ran for 7173ms\r\nAll tests done, failures: 3.\r\nExit with fail due to some tests failure.\r\n```\r\n\r\nI found in the following in trace logs, I don't know why `android_browser_4_4` is not recognized, but I don't think this is related.\r\n```\r\n[android 4.4, Android Browser null] client.createWorker | response: undefined Error: Validation Failed - `device` invalid\r\n at IncomingMessage.\u003canonymous\u003e (/home/travis/build/ncoden/foundation-sites/node_modules/browserstack/lib/client.js:73:9)\r\n at IncomingMessage.emit (events.js:187:15)\r\n at endReadableNT (_stream_readable.js:1090:12)\r\n at process._tickCallback (internal/process/next_tick.js:63:19)\r\nError from BrowserStack: Error: Validation Failed - `device` invalid\r\n at IncomingMessage.\u003canonymous\u003e (/home/travis/build/ncoden/foundation-sites/node_modules/browserstack/lib/client.js:73:9)\r\n at IncomingMessage.emit (events.js:187:15)\r\n at endReadableNT (_stream_readable.js:1090:12)\r\n at process._tickCallback (internal/process/next_tick.js:63:19)\r\n```\r\n\r\nSee also:\r\n* Browserstack config file: https://github.com/zurb/foundation-sites/blob/develop/browserstack.json\r\n* Full log: https://travis-ci.org/ncoden/foundation-sites/jobs/387169582\r\n* Full log with trace log level: https://travis-ci.org/ncoden/foundation-sites/jobs/387194396\r\n\r\n### Possible solution\r\n\r\nI checked at the source code. I have no problem with Node, but the code around the worker execution and results processing is very confusing. I am unable to propose a solution for now.\r\n\r\n","author":{"url":"https://github.com/ncoden","@type":"Person","name":"ncoden"},"datePublished":"2018-06-02T19:46:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/201/browserstack-runner/issues/201"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:535ee6a6-edf7-2b67-ca25-fa7fd0b620a2 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A06A:1E5465:263A3E7:35BC8EC:696F723B |
| html-safe-nonce | ebde6bd039670ed22e2f6349e06b14966d56643f0915b3dbb500c79184cee8ca |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBMDZBOjFFNTQ2NToyNjNBM0U3OjM1QkM4RUM6Njk2RjcyM0IiLCJ2aXNpdG9yX2lkIjoiODY5OTExMTM2MTA1ODE0MDczMSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 1f4a133627fd9b8320ed9721bb94874b4134509bceb93a0eb98fb6d8b081f8c6 |
| hovercard-subject-tag | issue:328771949 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/browserstack/browserstack-runner/201/issue_layout |
| twitter:image | https://opengraph.githubassets.com/2ac09c1824b04953716269e40ef1dbf93b188baaa70a676996cdfd44bbbf0503/browserstack/browserstack-runner/issues/201 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/2ac09c1824b04953716269e40ef1dbf93b188baaa70a676996cdfd44bbbf0503/browserstack/browserstack-runner/issues/201 |
| og:image:alt | Bug For unknown reasons, browserstack-runner sometimes exits with failures while all tests run without errors. For exemple see the following Travis job with mocha: all tests passed (or are skipped)... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | ncoden |
| hostname | github.com |
| expected-hostname | github.com |
| None | acc7f8c2e144976eeb6e7a73826049dd183bc572ccf5eaa9afb8265c617a97ab |
| turbo-cache-control | no-preview |
| go-import | github.com/browserstack/browserstack-runner git https://github.com/browserstack/browserstack-runner.git |
| octolytics-dimension-user_id | 1119453 |
| octolytics-dimension-user_login | browserstack |
| octolytics-dimension-repository_id | 11685362 |
| octolytics-dimension-repository_nwo | browserstack/browserstack-runner |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 11685362 |
| octolytics-dimension-repository_network_root_nwo | browserstack/browserstack-runner |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | cc546a224d6d4726a8d7c3a0dfe0cf65dbf9b7bd |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width