* [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
* add some retries, waiting for the loading indicator to be hidden once is not enough
* test to see if looping over the flaky test 25 times will trigger it on jenkins
* Try again to semi-reliably report on jenkins
* Attempt to fix invalid id coming out of getDashboardIdFromCurrentUrl
* Clean up to submit attempted flaky test failure fix
clean up
* Region map settings clarifications (#14893)
Improve documentation.
This also includes some additions to clarify the new includeElasticMapsService setting.
It also fully qualify all parameter names.
This fix ensures the render-complete event does not fire before rendering is actually completed.
- This ensures that the ChoroplethLayer is fully loaded, by explicitly waiting until all geojson files are loaded.
- It also removes the special init() code-path for coordinate-maps.This was the cause of coordinate-maps not showing on reports.
Reverts change in c1ef3d892f
If an error is raised before the logger is setup, then the server will exit without any notice.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
* [dev/ci_setup] generalize jenkins_setup script for other CI environments
* [dev/ci_setup] accept more general `CACHE_DIR` env arg
* [dev/ci_setup] node.js install might not be invalid
* Add url whitelist
* Use .some
* Add/fix tests
* Add browser tests
* Initial pass
* Different approach, and more tests
* Fix linting issues
* Special case relative urls starting with `#`
* Handle root relative link too
* Try this another way
* Reapply my changes
* Fix IE11 bug which caused kuiToolBarSearch to grow too wide when there is only a single kuiToolBarSection sibling.
* Fix bugs with KuiListingTableToolBar rendering empty sections. Update docs example to demonstrate a tool bar with a search and a section.
In 7.0 ES put a limit on the number of fields that a query can expand to. Since a search term without an explicit field selection hits all fields by default, a kibana user could get an error if the index they're searching against has more than 1024 fields. With lucene, the ES admin could fix this by changing the default_field in their index settings. Kuery still had a problem though, because multi_match did not support default_field. The ES team kindly added default_field support to multi_match for us, so this PR updates Kuery to rely on default_field when a user submits a query without an explicit field.
* [Logging] more tests and added robustness to log formatting
* empty string for default error message, along with TODO question comment
* try to use stack trace from error when there is no error message
* simplify using the stack as the default error message
* destructure get from lodash
* default no-message to static string instead of error stack
* fix tests
