Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing test: X-Pack Detection Engine API Integration Tests.x-pack/test/detection_engine_api_integration/security_and_spaces/tests/find_statuses·ts - detection engine api security and spaces enabled find_statuses "after each" hook for "should return a single rule status when a single rule is loaded from a find status with defaults added" #63776

Closed
kibanamachine opened this issue Apr 16, 2020 · 3 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Apr 16, 2020

A test failed on a tracked branch

{ Error: Conflict
    at respond (/dev/shm/workspace/kibana/node_modules/elasticsearch/src/lib/transport.js:349:15)
    at checkRespForFailure (/dev/shm/workspace/kibana/node_modules/elasticsearch/src/lib/transport.js:306:7)
    at HttpConnector.<anonymous> (/dev/shm/workspace/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:173:7)
    at IncomingMessage.wrapper (/dev/shm/workspace/kibana/node_modules/elasticsearch/node_modules/lodash/lodash.js:4929:19)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
  status: 409,
  displayName: 'Conflict',
  message: 'Conflict',
  path: '/.kibana/_delete_by_query',
  query:
   { q: 'type:siem-detection-engine-rule-status', refresh: true },
  body:
   { took: 5,
     timed_out: false,
     total: 1,
     deleted: 0,
     batches: 1,
     version_conflicts: 1,
     noops: 0,
     retries: { bulk: 0, search: 0 },
     throttled_millis: 0,
     requests_per_second: -1,
     throttled_until_millis: 0,
     failures: [ [Object] ] },
  statusCode: 409,
  response:
   '{"took":5,"timed_out":false,"total":1,"deleted":0,"batches":1,"version_conflicts":1,"noops":0,"retries":{"bulk":0,"search":0},"throttled_millis":0,"requests_per_second":-1.0,"throttled_until_millis":0,"failures":[{"index":".kibana_1","id":"siem-detection-engine-rule-status:be79d730-8026-11ea-9aa7-3bfd46755bd5","cause":{"type":"version_conflict_engine_exception","reason":"[siem-detection-engine-rule-status:be79d730-8026-11ea-9aa7-3bfd46755bd5]: version conflict, required seqNo [1208], primary term [1]. current document has seqNo [1210] and primary term [1]","index_uuid":"dp7pqWX1SnawX2sL3TL4ZQ","shard":"0","index":".kibana_1"},"status":409}]}',
  toString: [Function],
  toJSON: [Function] }

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Apr 16, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage (failed-test)

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@rylnd
Copy link
Contributor

rylnd commented Apr 17, 2020

@dhurley14 any thoughts on what might have caused this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test
Projects
None yet
Development

No branches or pull requests

4 participants