Failing test: X-Pack Detection Engine API Integration Tests.x-pack/test/detection_engine_api_integration/security_and_spaces/group9/exception_operators_data_types/text_array·ts - detection engine api security and spaces enabled - Group 9 Detection exceptions data types and operators Rule exception operators for data type text "is in list" operator will return 4 results if we have two lists with an AND contradiction text === "word one" AND text === "word five"

[kibanamachine]

A test failed on a tracked branch

Error: expected [ [],
  [ 'word five', null, 'word six', 'word seven' ],
  [ 'word one', 'word two', 'word three', 'word four' ] ] to sort of equal [ [],
  [ 'word eight', 'word nine', 'word ten' ],
  [ 'word five', null, 'word six', 'word seven' ],
  [ 'word one', 'word two', 'word three', 'word four' ] ]
    at Assertion.assert (expect.js:100:11)
    at Assertion.eql (expect.js:244:8)
    at Context.<anonymous> (text_array.ts:403:25)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Object.apply (wrap_function.js:73:16) {
  actual: '[\n' +
    '  []\n' +
    '  [\n' +
    '    "word five"\n' +
    '    [null]\n' +
    '    "word six"\n' +
    '    "word seven"\n' +
    '  ]\n' +
    '  [\n' +
    '    "word one"\n' +
    '    "word two"\n' +
    '    "word three"\n' +
    '    "word four"\n' +
    '  ]\n' +
    ']',
  expected: '[\n' +
    '  []\n' +
    '  [\n' +
    '    "word eight"\n' +
    '    "word nine"\n' +
    '    "word ten"\n' +
    '  ]\n' +
    '  [\n' +
    '    "word five"\n' +
    '    [null]\n' +
    '    "word six"\n' +
    '    "word seven"\n' +
    '  ]\n' +
    '  [\n' +
    '    "word one"\n' +
    '    "word two"\n' +
    '    "word three"\n' +
    '    "word four"\n' +
    '  ]\n' +
    ']',
  showDiff: true
}

First failure: CI Build - main

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[WafaaNasr]

After successfully running this test through the Flaky Test Runner for 100 iterations without any failures, it has been determined that the test is not truly flaky or failing. As a result, the ticket can be closed.