Failing test: X-Pack Alerting API Integration Tests.x-pack/test/alerting_api_integration/security_and_spaces/tests/alerting/update·ts - alerting api integration security and spaces enabled Alerts alerts update "after all" hook in "update"

[kibanamachine]

A test failed on a tracked branch

Error: expected 204 "No Content", got 409 "Conflict"
    at Test._assertStatus (/dev/shm/workspace/parallel/19/kibana/node_modules/supertest/lib/test.js:268:12)
    at Test._assertFunction (/dev/shm/workspace/parallel/19/kibana/node_modules/supertest/lib/test.js:283:11)
    at Test.assert (/dev/shm/workspace/parallel/19/kibana/node_modules/supertest/lib/test.js:173:18)
    at assert (/dev/shm/workspace/parallel/19/kibana/node_modules/supertest/lib/test.js:131:12)
    at /dev/shm/workspace/parallel/19/kibana/node_modules/supertest/lib/test.js:128:5
    at Test.Request.callback (/dev/shm/workspace/parallel/19/kibana/node_modules/supertest/node_modules/superagent/lib/node/index.js:718:3)
    at /dev/shm/workspace/parallel/19/kibana/node_modules/supertest/node_modules/superagent/lib/node/index.js:906:18
    at IncomingMessage.<anonymous> (/dev/shm/workspace/parallel/19/kibana/node_modules/supertest/node_modules/superagent/lib/node/parsers/json.js:19:7)
    at endReadableNT (internal/streams/readable.js:1317:12)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)

First failure: Jenkins Build

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[kibanamachine]

New failure: Jenkins Build

[spalger]

Loads of recent failures

Skipped
master/8.0: 38d08c4
7.x/7.16: 8b26ec5

[pmuellr]

I think this is from here!?!?!:

kibana/x-pack/test/alerting_api_integration/security_and_spaces/tests/alerting/update.ts

Line 39 in c7ee7d7

after(() => objectRemover.removeAll());

Here's that code:

kibana/x-pack/test/alerting_api_integration/common/lib/object_remover.ts

Lines 34 to 44 in c7ee7d7

	async removeAll() {
	await Promise.all(
	this.objectsToRemove.map(({ spaceId, id, type, plugin }) => {
	return this.supertest
	.delete(`${getUrlPrefix(spaceId)}/api/${plugin}/${type}/${id}`)
	.set('kbn-xsrf', 'foo')
	.expect(204);
	})
	);
	this.objectsToRemove = [];
	}

Not clear how we could get a 409 on a delete with no OCC. correction: I assumed this was a SO delete, but of course it's a rule delete, so there's likely some OCCish stuff there ... OR it could actually be a connector delete ...

[mikecote]

Seems like the switch to multiple-isolated makes this function return versioning (by passing in a non-empty preflightResult now) which will cause the delete to return 409 (docs) if the document is updated between the read/delete calls.