Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delay in runtests-browser #23877

Closed
ghost opened this issue May 3, 2018 · 5 comments
Closed

Delay in runtests-browser #23877

ghost opened this issue May 3, 2018 · 5 comments
Assignees
Labels
Infrastructure Issue relates to TypeScript team infrastructure

Comments

@ghost
Copy link

ghost commented May 3, 2018

As of #20763, it's taking a lot longer to bring up runtests-browser. I've tested this in two parallel checkouts, one in #23875 and one in the commit prior to #20763 (24e58c3).
First I ran gulp runtests-browser in both to ensure everything was built. Then running gulp runtests-browser --test findAllRefs in both:

There is also a delay when refreshing the window -- so If I missed something and have to restart, I have to wait 30 seconds to begin debugging again.

@ghost ghost added the Infrastructure Issue relates to TypeScript team infrastructure label May 3, 2018
@ghost
Copy link
Author

ghost commented May 7, 2018

unresponsive

@mhegazy
Copy link
Contributor

mhegazy commented May 8, 2018

I am seeing that too locally after @rbuckton’s vfs change

@rbuckton
Copy link
Member

rbuckton commented May 8, 2018

I can take a look first thing tomorrow. I think it has something to do with caching.

@ghost
Copy link
Author

ghost commented May 8, 2018

I had exception breakpoints turned on and it also looks like we throw a lot of exceptions in vfs.ts on startup -- not sure if that's the cause though.

@sheetalkamat
Copy link
Member

I have had trouble with lot of exceptions being thrown. Everytime i make some change, i need to go ahead and disable the breakpoints at those exception sites.

@microsoft microsoft locked and limited conversation to collaborators Jul 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Infrastructure Issue relates to TypeScript team infrastructure
Projects
None yet
Development

No branches or pull requests

3 participants