On Wed, 2 Sep 2020 11:12:53 +0200 (CEST) Johannes Schindelin wrote: > On Wed, 2 Sep 2020, Takashi Yano wrote: > > OK, I will check Angular/CLI next. But I am not familier with > > Agnular/CLI. Could you please provide simple steps to reproduce > > the problem? > > Here is a report: https://github.com/git-for-windows/git/issues/2793
I already read that thread, and I have try following step. 1) Install node.js 2) npm install --global @angular/cli 3) ng new test-app 4) cd test-app 5) ng test --code-coverage However, the output is very differnt from the bug report, and there seems to be no garbled output. The output is something like: Compiling @angular/core : es2015 as esm2015 Compiling @angular/animations : es2015 as esm2015 Compiling @angular/compiler/testing : es2015 as esm2015 Compiling @angular/common : es2015 as esm2015 Compiling @angular/animations/browser : es2015 as esm2015 Compiling @angular/core/testing : es2015 as esm2015 Compiling @angular/animations/browser/testing : es2015 as esm2015 Compiling @angular/platform-browser : es2015 as esm2015 Compiling @angular/common/http : es2015 as esm2015 Compiling @angular/common/testing : es2015 as esm2015 Compiling @angular/router : es2015 as esm2015 Compiling @angular/forms : es2015 as esm2015 Compiling @angular/platform-browser-dynamic : es2015 as esm2015 Compiling @angular/platform-browser/testing : es2015 as esm2015 Compiling @angular/platform-browser/animations : es2015 as esm2015 Compiling @angular/common/http/testing : es2015 as esm2015 Compiling @angular/platform-browser-dynamic/testing : es2015 as esm2015 Compiling @angular/router/testing : es2015 as esm2015 10% building 2/2 modules 0 active02 09 2020 23:49:25.110:WARN [karma]: No captur ed browser, open http://localhost:9876/ 02 09 2020 23:49:25.118:INFO [karma-server]: Karma v5.0.9 server started at http ://0.0.0.0:9876/ 02 09 2020 23:49:25.119:INFO [launcher]: Launching browsers Chrome with concurre ncy unlimited 02 09 2020 23:49:25.125:INFO [launcher]: Starting browser Chrome 92% additional asset processing copy-webpack-plugin02 09 2020 23:49:34.003:WARN [karma]: No captured browser, open http://localhost:9876/ 02 09 2020 23:49:34.907:INFO [Chrome 85.0.4183.83 (Windows 10)]: Connected on so cket z7khH23JfW4v-_TtAAAA with id 59608191 Chrome 85.0.4183.83 (Windows 10): Executed 3 of 3 SUCCESS (0.62 secs / 0.273 sec s) TOTAL: 3 SUCCESS TOTAL: 3 SUCCESS TOTAL: 3 SUCCESS =============================== Coverage summary =============================== Statements : 100% ( 6/6 ) Branches : 100% ( 0/0 ) Functions : 100% ( 0/0 ) Lines : 100% ( 5/5 ) ================================================================================ What's wrong? > But why do you want to look into Angular/CLI? Do you really think that it > makes sense to try to fix every console app out there? Really? Wouldn't it > make more sense to just accept that there are many console applications > that are broken by the recent change, and accommodate them in the Cygwin > runtime? That would take substantially less time. It is important to know what's happning actually to fix the issue. Superficial patch makes the problem more complicated. -- Takashi Yano <takashi.y...@nifty.ne.jp>