Repository navigation
ci: Unexpected end of JSON input flakes on test_docs_examples_ivy #31842
Description
I've been occasionally seeing the following flakes recently on test_docs_examples_ivy CircleCI jobs. (They are not related to a specific example and/or port.)
They might be related to ngcc processing (see #30593).
running: yarn e2e --prod --no-webdriver-update --port=4010
...
chunk {0} runtime.858f8dd898b75fe86926.js, runtime.858f8dd898b75fe86926.js.map (runtime) 1.46 kB [entry] [rendered]
chunk {1} main.7ad9d3bff607835cd780.js, main.7ad9d3bff607835cd780.js.map (main) 140 kB [initial] [rendered]
chunk {2} polyfills.12f05dd60a9f2606773d.js, polyfills.12f05dd60a9f2606773d.js.map (polyfills) 189 bytes [initial] [rendered]
chunk {3} polyfills-es5.fda5b2b92895a7fccf2b.js, polyfills-es5.fda5b2b92895a7fccf2b.js.map (polyfills-es5) 68.1 kB [initial] [rendered]
chunk {4} styles.5a0929e8dea91c06925b.css, styles.5a0929e8dea91c06925b.css.map (styles) 824 bytes [initial] [rendered]
ERROR in Unexpected end of JSON input
...
Sample failures:
- 400384#1 (
examples/bootstrapping) - 400384#2 (
examples/elements) - 402919#3 (
examples/built-in-template-functions) - 411013#0 (
examples/dynamic-component-loader) - 411033#4 (
examples/feature-modules) - 411282#3 (
examples/built-in-template-functions) - 411529#1 ('examples/router`)
UPDATE [2019-08-03]: Maybe coincidence, but I noticed in the above failures it is always either the 2nd, 4th or 8th cli (i.e. non-SystemJS) example that fails (all even numbers) 🤔
Activity
[-]ci: `Unexpected end of JSON input` flakes on `test_docs_examples[_ivy]`[/-][+]ci: `Unexpected end of JSON input` flakes on `test_docs_examples_ivy`[/+]gkalpak commentedon Jul 25, 2019
FWIW, I wasn't able to reproduce it by ssh'ing into a container and running the docs examples e2e tests ~25 times 😞
Also, checked
@angular/core/package.jsonbefore and afterng e2eand there aren't any differences (meaningngccdoesn't need to update thepackage.jsonduring the cli build (for the@angular/corepackage at least)).gkalpak commentedon Sep 5, 2019
Interestingly, when this job failed with that error and I ssh'd into the VM and rerun (
yarn example-e2e --filter=attribute-directives- i.e. without touchingnode_modules/) it passed.So, it might not be
ngccrelated after all 🎉It looks like a "regular" (cli-related?) flake 🤔
ci: re-run flaky docs examples e2e tests in `test_docs_examples[_ivy]…
ci: re-run flaky docs examples e2e tests in `test_docs_examples[_ivy]…
angular-automatic-lock-bot commentedon Oct 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.