In large apps with very large heapsnapshots, CI builds are timing out, even after memory leak detection results show up in the build/test CI logs. Unclear what is going on, but in these cases it can take several minutes for the heap snapshot to be parsed. There may be a timeout somewhere in testem config or similar that needs to be increased. I've been able to replicate these timeouts/unfinished test runs locally on the app in question, so its likely something with testem.
Whatever is determined to be causing the test timeouts should be documented.
In large apps with very large heapsnapshots, CI builds are timing out, even after memory leak detection results show up in the build/test CI logs. Unclear what is going on, but in these cases it can take several minutes for the heap snapshot to be parsed. There may be a timeout somewhere in testem config or similar that needs to be increased. I've been able to replicate these timeouts/unfinished test runs locally on the app in question, so its likely something with testem.
Whatever is determined to be causing the test timeouts should be documented.