[TIMOB-23776] Windows: Investigate failing mocha tests on Jenkins
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2016-10-04T23:28:54.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 6.0.0 |
| Components | Windows |
| Labels | n/a |
| Reporter | Gary Mathews |
| Assignee | Kota Iguchi |
| Created | 2016-08-15T16:23:56.000+0000 |
| Updated | 2016-10-07T14:52:18.000+0000 |
Description
Investigate why certain tests fail on Windows Desktop, recently we have needed to disable a number of tests that have prevented the Jenkins builds from passing. We should investigate into why this is happening and try to re-enable the test cases that previously failed.
We have been seeing
setTimeoutfreezes intermittently on Jenkins. I'm looking into it.I have been pushing potential fix for it [PR 847](https://github.com/appcelerator/titanium_mobile_windows/pull/847) and I can see the series of changes I made fixes the issue on Windows 10 so far (y) - Avoid use of JSObject for storing Timer callback because it is heavy weight operation with few benefits. - Avoid using
0interval forsetTimeout. It intermittently freezesDispatcherTimer. - Update JavaScriptCore, it fixes the intermittent crash issue on Windows 10. We are able to re-enable failing UI tests too. Note that it does not fix the issue on Windows 8.1. It's because Windows 8.1 and Windows Phone 8.1 is missing required function ([GetThreadContext](https://msdn.microsoft.com/en-us/library/windows/desktop/ms679362(v=vs.85).aspx)) and currently I don't have a workaround for it.All UI tests are now enabled, Jenkins seems to be working better so far. PR: https://github.com/appcelerator/titanium_mobile_windows/pull/863.
Dev task. Closing