* Bump node to 6.17.0
* Resolve intermittent premature connection closed (#19808)
Node 8 changed the keepAlive to default to 5 seconds from 5 minutes. This reverts that behavior.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
* 6
Changelog:
- [6.15.0](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V6.md#6.15.0)
`index result popularity change popularity should be reset on cancel` has been skipped. This particular test exhibited weird behavior in Chrome when controlled by Selenium. When the button to confirm deleting the index pattern was clicked, it would result in multiple (3-5) calls to the delete saved object endpoint, though only one of those calls was represented in the network tab.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
This backports #23422 to the 5.6 branch.
## Implementation Notes
The original fix for #23422 takes advantage of [yarn aliases](https://yarnpkg.com/lang/en/docs/cli/add/#toc-yarn-add-alias) to link to the forked version of lodash. Kibana 5.x does not use yarn, but rather npm. npm does not support aliases, so we are not able to cleanly backport this change.
We first attempted to point to the git repository directly (`elastic/lodash@3.10.1-npm-kibana1`), but its `package.json` correctly names the package `@elastic/lodash`. When installing this package, we end up with an `@elastic/lodash` directory in `node_modules`, rather than a `lodash` directory. Since we are missing the `lodash` directory, all import/require statements for `lodash` fail.
This PR solves that by publishing a nearly identical branch which is named `lodash` instead of `@elastic/lodash`: https://github.com/elastic/lodash/tree/3.10.1-npm-kibana1-5.6.
This is admittedly a hacky solution, but this is a temporary fix, and we do not anticipate making many/any changes to the 'lodash' fork for 5.6.
* [dev/mocha/junit] report real skipped test count and errors from hooks (#15465)
* [dev/mocha/junit] report real skipped test count and errors from hooks
* typo
* [grunt/simplemocha] update simplemocha patterns to exclude fixtures
* [CI] Produce junit test reports (#15281)
* [mocha] use custom reporter for legible results in jenkins
* [jest] use custom result processor for legible results in jenkins
* [karma] enable junit output on CI
* [mocha/junitReporter] accept rootDirectory as configuration
* [jest/reporter] use reporters option added in jest 20
* [toolingLog] remove black/white specific colors
* [dev/mocha/junit] no reason for junit to be a "reporter"
* typos
* [dev/mocha/junit] use else if
* [karma/junit] use string#replace for explicitness
* [junit] use test file path as "classname"
* [ftr/mocha] no longer a "console" specific reporter
* [dev/jest] fix relative path to babel options
* [partial backport] extract kbnServer test utils from #12554
* Implement esTestCluster test util (#13099)
* [es/tests] remove unused module
* [testUtil/es] add utility for starting es nodes in tests
* [ftr/tests] use esTestCluster util to start es
* [es/tests/routes] use esTestCluster to start own es
* [testUtils/kbnServer] disable uiSettings unless plugins are enabled
* [testUtils/esTestCluster] use standard test es port by default
* [server/http/tests] add esTestCluster to setup
* [test/config] unify es test config into a single module
* [testUtils/esTestCluster] directory is no longer configurable
* [testUtils/esTestCluster] throw when es.start() is called again without es.stop()
* [testUtils/esTestCluster] is* checks should not mutate state
(cherry picked from commit 6748b22d03)
* [testUtils/esTestCluster] use more standard api style (#13197)
(cherry picked from commit d36080bca8)
* [scanner] use new esTestConfig service
