Failing test: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/spaces_only/tests/alerting/builtin_alert_types/es_query/alert·ts - alerting api integration spaces only Alerting builtin alertTypes es_query alert runs correctly: use epoch millis - threshold on hit count < > for searchSource search type

[kibanamachine]

A test failed on a tracked branch

Error: expected '' to not be empty
    at Assertion.assert (/var/lib/buildkite-agent/builds/kb-n2-4-spot-f90511d06ddfb238/elastic/kibana-on-merge/kibana/node_modules/@kbn/expect/expect.js:100:11)
    at Assertion.empty (/var/lib/buildkite-agent/builds/kb-n2-4-spot-f90511d06ddfb238/elastic/kibana-on-merge/kibana/node_modules/@kbn/expect/expect.js:209:8)
    at Function.empty (/var/lib/buildkite-agent/builds/kb-n2-4-spot-f90511d06ddfb238/elastic/kibana-on-merge/kibana/node_modules/@kbn/expect/expect.js:531:15)
    at Context.<anonymous> (test/alerting_api_integration/spaces_only/tests/alerting/builtin_alert_types/es_query/alert.ts:234:34)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Object.apply (/var/lib/buildkite-agent/builds/kb-n2-4-spot-f90511d06ddfb238/elastic/kibana-on-merge/kibana/node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/wrap_function.js:87:16)

First failure: CI Build - main

[kibanamachine]

New failure: CI Build - main

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[spalger]

Looks like this test is new as of 5 days ago from #124534 cc @dmitriynj

This has failed a ton in PRs, skipping for now

Skipped
main/8.3: f5d008e

[ymao1]

Looks like this test is failing with this error for the search source query:

{
	"type": "status_exception",
	"reason": "error while executing search",
	"caused_by": {
		"type": "search_phase_execution_exception",
		"reason": "all shards failed",
		"phase": "query",
		"grouped": true,
		"failed_shards": [{
			"shard": 0,
			"index": ".kibana-alerting-test-data",
			"node": "RSfnBKqBTm6o6y4lge8iAQ",
			"reason": {
				"type": "parse_exception",
				"reason": "failed to parse date field [2022-05-26T17:25:49.010Z] with format [epoch_millis]: [failed to parse date field [2022-05-26T17:25:49.010Z] with format [epoch_millis]]",
				"caused_by": {
					"type": "illegal_argument_exception",
					"reason": "failed to parse date field [2022-05-26T17:25:49.010Z] with format [epoch_millis]",
					"caused_by": {
						"type": "date_time_parse_exception",
						"reason": "Failed to parse with all enclosed parsers"
					}
				}
			}
		}]
	}
}

[ymao1]

@kertal I am unskipping this test suite in this PR so I can add a test for the recovery context. I commented out the specific search source test that was being flaky and pasted the error I was seeing in that test in the above comment.