Sri Harsha Pamu

I am not really sure if this is an expected behavior and has been purposefully designed this way. If it is, then I don't have any complaints. But would be...

Right. When the specs are ran, at the end, I can see the list of specs. Will try to look into a fix :)

@saimaheshgaya That is not going to resolve the issue. If you increase the timeout to x, it times out after those x ms.

Same here! Hey @vargarobert I have posted the issue on the puppeteer's repo and they closed mine asking me to remove karma and try it out. I have to do...

@vargarobert That's cool. So, its clearly a problem with the `karma-chrome-launcher` then. I hope this problem gets the attention to the dev's on the team.

Thanks a lot @kumvem for the information. Yes, I did report it on the puppeteer. I didn't had any problems on OSX either. And the log which I shared is...

@kumvem I removed puppeteer, and also the customLaunchers property in the config. As the base property in the customLaunchers was assigned to `Chrome`, the `Starting browser Chrome` was logged. This...

@vargarobert any luck?

Thanks for sharing the info @vargarobert I wish it was as simple as Phantom JS though.

@kumvem I didn't get the timeout issue on Mac at all. seems like you misunderstood. I am getting timeout problem when executing on linux box.