-
Notifications
You must be signed in to change notification settings - Fork 0
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
[CLOSED] Some integration and extension tests fail when running all #3142
Comments
Comment by RaymondLim Not sure it's only me. I can consistently reproduce one unit test failure both on my win7 and mac 10.8.2. The unit test failing is "Live Development startup and shutdown". |
Comment by njx Reviewed. To |
Comment by redmunds FBNC for |
Comment by jasonsanjose Removed FBNC. #3628 was just a first step in re-arranging how we run tests on Jenkins. They are still failing more often than not. The new Jenkins jobs give us some more flexibility in how we run the tests and how we capture the results. |
Comment by jasonsanjose Removing Sprint 24 milestone |
Comment by njx Moved to sprint 26 |
Comment by jasonsanjose Too late to land for sprint 26. Punting to sprint 27. |
Issue by jasonsanjose
Thursday Apr 04, 2013 at 18:50 GMT
Originally opened as adobe/brackets#3343
When running
grunt test-integration --suite=all
, the following suites see intermittent failures: Live Development, StaticServer, NodeConnection. All of these suites rely onNodeConnection
. It's not clear why they pass in isolation, but fail in the overall "all" suite. Below is a sample of the failures due to timeout.The text was updated successfully, but these errors were encountered: