Title: ng test not working after upgrade to 6.0.0 · Issue #10485 · angular/angular-cli · GitHub
Open Graph Title: ng test not working after upgrade to 6.0.0 · Issue #10485 · angular/angular-cli
X Title: ng test not working after upgrade to 6.0.0 · Issue #10485 · angular/angular-cli
Description: After upgrading the cli the unit tests doesn't start anymore. Previous behaviour was that the unit tests were found and executed. Now it does not find the unit tests and says 0 of 0 executed. Versions Angular CLI: 6.0.0-rc.6 Node: 9.7.1 ...
Open Graph Description: After upgrading the cli the unit tests doesn't start anymore. Previous behaviour was that the unit tests were found and executed. Now it does not find the unit tests and says 0 of 0 executed. Versi...
X Description: After upgrading the cli the unit tests doesn't start anymore. Previous behaviour was that the unit tests were found and executed. Now it does not find the unit tests and says 0 of 0 executed. V...
Opengraph URL: https://github.com/angular/angular-cli/issues/10485
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ng test not working after upgrade to 6.0.0","articleBody":"After upgrading the cli the unit tests doesn't start anymore. \r\nPrevious behaviour was that the unit tests were found and executed. Now it does not find the unit tests and says 0 of 0 executed.\r\n\r\n### Versions\r\n```\r\nAngular CLI: 6.0.0-rc.6\r\nNode: 9.7.1\r\nOS: win32 x64\r\nAngular: 5.2.2\r\n... animations, common, compiler, compiler-cli, core, forms\r\n... http, language-service, platform-browser\r\n... platform-browser-dynamic, platform-server, router\r\n... service-worker\r\n```\r\n\r\n### Repro steps\r\n\r\n1. Upgrade to latest cli\r\n2. ng test\r\n\r\n### Observed behavior\r\n```\r\n27 04 2018 14:59:35.185:INFO [karma]: Karma v1.7.1 server started at http://0.0.0.0:9876/\r\n27 04 2018 14:59:35.191:INFO [launcher]: Launching browser Chrome with unlimited concurrency\r\n27 04 2018 14:59:35.201:INFO [launcher]: Starting browser Chrome 27 04 2018 15:00:26.221:INFO [Chrome 66.0.3359 (Windows 10 0.0.0)]: Connected on socket _q17vZKEaK6MoqgCAAAA with id 70169079\r\nChrome 66.0.3359 (Windows 10 0.0.0): Executed 0 of 0 ERROR (0.016 secs / 0 secs)\r\nnpm ERR! code ELIFECYCLE\r\nnpm ERR! errno 1\r\nnpm ERR! myproj-web@0.0.1 test: `ng test`\r\nnpm ERR! Exit status 1\r\nnpm ERR!\r\nnpm ERR! Failed at the myproj-web@0.0.1 test script.\r\nnpm ERR! This is probably not a problem with npm. There is likely additional logging output above.\r\n\r\nnpm ERR! A complete log of this run can be found in:\r\nnpm ERR! C:\\Users\\myuser\\AppData\\Roaming\\npm-cache\\_logs\\2018-04-27T13_00_28_789Z-debug.log\r\n```\r\n\r\n```\r\n10 silly lifecycle myproj-web@0.0.1~test: Args: [ '/d /s /c', 'ng test' ]\r\n11 silly lifecycle myproj-web@0.0.1~test: Returned: code: 1 signal: null\r\n12 info lifecycle myproj-web@0.0.1~test: Failed to exec test script\r\n13 verbose stack Error: myproj-web@0.0.1 test: `ng test`\r\n13 verbose stack Exit status 1\r\n13 verbose stack at EventEmitter.\u003canonymous> (C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\npm-lifecycle\\index.js:285:16)\r\n13 verbose stack at EventEmitter.emit (events.js:127:13)\r\n13 verbose stack at ChildProcess.\u003canonymous> (C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\npm-lifecycle\\lib\\spawn.js:55:14)\r\n13 verbose stack at ChildProcess.emit (events.js:127:13)\r\n13 verbose stack at maybeClose (internal/child_process.js:936:16)\r\n13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)\r\n14 verbose pkgid myproj-web@0.0.1\r\n15 verbose cwd C:\\Users\\myuser\\myproj\\myproj-web\r\n16 verbose Windows_NT 10.0.16299\r\n17 verbose argv \"C:\\\\Program Files\\\\nodejs\\\\node.exe\" \"C:\\\\Program Files\\\\nodejs\\\\node_modules\\\\npm\\\\bin\\\\npm-cli.js\" \"run\" \"test\"\r\n18 verbose node v9.7.1\r\n19 verbose npm v5.6.0\r\n20 error code ELIFECYCLE\r\n21 error errno 1\r\n22 error myproj-web@0.0.1 test: `ng test`\r\n22 error Exit status 1\r\n23 error Failed at the myproj-web@0.0.1 test script.\r\n23 error This is probably not a problem with npm. There is likely additional logging output above.\r\n24 verbose exit [ 1, true ]\r\n```\r\n","author":{"url":"https://github.com/DominicBoettger","@type":"Person","name":"DominicBoettger"},"datePublished":"2018-04-27T14:17:51Z","url":"https://github.com/angular/angular-cli/issues/10485"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| 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:68b2d3bb-58e7-317b-6d67-88fb904ba7e1 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | BB34:63875:AA4A0F:E35385:6B00EC22 |
| html-safe-nonce | 7571066a7138ee58a0e75cdaefdf287374c1626c136ee86b7779b06c2d53345c |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCQjM0OjYzODc1OkFBNEEwRjpFMzUzODU6NkIwMEVDMjIiLCJ2aXNpdG9yX2lkIjoiNTMwNjMxNTc4Mzk5Mzg3OTU4NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 4b4047b8035163fb6487116c1cd65de868376d5f96aa89a4ebd6aa9743fedbb0 |
| hovercard-subject-tag | issue:318426926 |
| 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/angular/angular-cli/10485/issue_layout |
| twitter:image | https://opengraph.githubassets.com/bb879d025f233f2bf131bd980fd5f1b7b5c2de72c8df30067942bd4b1b2c11b8/angular/angular-cli/issues/10485 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/bb879d025f233f2bf131bd980fd5f1b7b5c2de72c8df30067942bd4b1b2c11b8/angular/angular-cli/issues/10485 |
| og:image:alt | After upgrading the cli the unit tests doesn't start anymore. Previous behaviour was that the unit tests were found and executed. Now it does not find the unit tests and says 0 of 0 executed. Versi... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | DominicBoettger |
| hostname | github.com |
| expected-hostname | github.com |
| None | 4ef498cbabcbe3c50befc7a5b743e7072ee770b4daf0e15e54801180d1fa91fc |
| turbo-cache-control | no-preview |
| go-import | github.com/angular/angular-cli git https://github.com/angular/angular-cli.git |
| octolytics-dimension-user_id | 139426 |
| octolytics-dimension-user_login | angular |
| octolytics-dimension-repository_id | 36891867 |
| octolytics-dimension-repository_nwo | angular/angular-cli |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 36891867 |
| octolytics-dimension-repository_network_root_nwo | angular/angular-cli |
| 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 | 9983dd5da06943f833c971dd5b6bc988e2858be5 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width