88427e9a43
The tests in master are currently failing regularly because our current browser tests are serious memory hogs. Investigation reveals that nearly every test is retaining all of the memory it causes to be allocated. We have made some progress to being able to diagnose the problems, but we expect that problem to take some serious work to fix. We need a short-term solution though, and this is it. Rather than modify the bundling process, we will shard the top-level test suites by name. For now, we've created 4 shards, but adding new shards is trivial if we need to. Sharding is accomplished by creating a murmur3 hash of the top level suite names, then bucketing based on the hash output. If a test suite resolves to shard2, but we are running shard1, we simply never pass the function to `mocha.describe()`. Rather than redefine every describe statement, we have shimmed the global `window.describe()` function to accomplish this. |
||
|---|---|---|
| .. | ||
| build | ||
| config | ||
| utils | ||
| check_added_filenames.js | ||
| collect_files_to_commit.js | ||
| jenkins.js | ||
| licenses.js | ||
| lint_staged_files.js | ||
| plugin.js | ||
| precommit.js | ||
| reject_rej_files.js | ||
| release.js | ||
| release_packages.js | ||
| setup_kibana.js | ||
| sterilize.js | ||
| test.js | ||