Open kibanamachine opened 11 months ago
Pinging @elastic/security-defend-workflows (Team:Defend Workflows)
@ashokaditya maybe some retry logic on this will help. The unavailable resource is, perhaps, transient but retrying it could reduce flakiness. We can keep an eye on this and see if it happens again
New failure: CI Build - main
Pinging @elastic/security-solution (Team: SecuritySolution)
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
Fixed here: https://github.com/elastic/kibana/pull/173589 cc: @ashokaditya
New failure: CI Build - 8.12
New failure: CI Build - 8.12
New failure: CI Build - 8.12
New failure: CI Build - 8.12
/skip
Skipped
8.12: 57e705feb817d0e2fc7d16868f3b82a95d6d1a8c
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
/skip
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
A test failed on a tracked branch
First failure: CI Build - main