test(docs-infra): 404 for images during unit tests on Windows

[gkalpak]

Running the unit tests for aio on Windows, many 404s are logged for images, resulting in progress logs being spread over multiple lines:

Chrome 70.0.3538 (Linux 0.0.0): Executed 0 of 609 SUCCESS (0 secs / 0 secs)
Chrome 70.0.3538 (Linux 0.0.0): Executed 1 of 609 SUCCESS (0 secs / 0.304 secs)
Chrome 70.0.3538 (Linux 0.0.0): Executed 2 of 609 SUCCESS (0 secs / 0.355 secs)
Chrome 70.0.3538 (Linux 0.0.0): Executed 3 of 609 SUCCESS (0 secs / 0.395 secs)
Chrome 70.0.3538 (Linux 0.0.0): Executed 4 of 609 SUCCESS (0 secs / 0.438 secs)
Chrome 70.0.3538 (Linux 0.0.0): Executed 5 of 609 SUCCESS (0 secs / 0.471 secs)
Chrome 70.0.3538 (Linux 0.0.0): Executed 6 of 609 SUCCESS (0 secs / 0.504 secs)
Chrome 70.0.3538 (Linux 0.0.0): Executed 7 of 609 SUCCESS (0 secs / 0.542 secs)
Chrome 70.0.3538 (Linux 0.0.0): Executed 8 of 609 SUCCESS (0 secs / 0.578 secs)
Chrome 70.0.3538 (Linux 0.0.0): Executed 9 of 609 SUCCESS (0 secs / 0.621 secs)
...

For example, running this test, I get:

WARN [web-server]: 404: /assets/images/logos/angular/logo-nav@2x.png
WARN [web-server]: 404: /assets/images/logos/angular/angular_whiteTransparent_withMargin.png

I was not able to reproduce it on a new project on Windows 🤷‍♂️
It also works fine on Linux and Windows Subsystem for Linux for aio/ as well 😕

[sonukapoor]

@gkalpak I am not able to reproduce this either on my Windows 10 Laptop:

[gkalpak]

Interesting. I can still reproduce i (although with much fewer occurrences, so only a couple of extra lines). Based on the screenshot, you seem to only have run 1 tests; maybe that's the reason you don't see the problem?

_{In any case, thanks for looking into this @sonukapoor ❤️}

[sonukapoor]

@gkalpak, I got the latest and re-ran all tests. I am still not able to reproduce this:

[gkalpak]

Well, you actually did reproduce it 😁
The reason you have three lines with "...Executed xyz of 621..." is because something was written to the terminal. It is definitely much better than before, so it seems that the main issue was fixed.

It would still be interesting to find out what is being printed and whether we can get rid of it (e.g. by using a different jasmine reporter).

[sonukapoor]

You got it. I am on it

[sonukapoor]

@gkalpak Please assign this one to me, so I can track it. Thanks