Open kibanamachine opened 2 years ago
Pinging @elastic/kibana-presentation (Team:Presentation)
New failure: CI Build - 7.17
New failure: CI Build - 7.17
Closing, no failures in last 30 days
New failure: CI Build - 7.17
Related: https://github.com/elastic/kibana/issues/136459
The failure only seems to happen on 7.17, and we don't have access to the flaky test runner for this version as noted by Tim here. Not sure how we go about fixing this if that is the case - or if there is even a reason to? It seems like it may just be linked to a Mocha failure (from the previously linked test failure) sooo... not sure if there's even much to be done here 👀
The failure only seems to happen on 7.17, and we don't have access to the flaky test runner for this version as noted by Tim https://github.com/elastic/kibana/pull/143716#issuecomment-1289379135. Not sure how we go about fixing this if that is the case - or if there is even a reason to? It seems like it may just be linked to a Mocha failure (from the previously linked test failure) sooo... not sure if there's even much to be done here 👀
Ya, let's just close. Focusing on flaky tests in main is time consuming enough.
New failure: CI Build - 7.17
Closing - same 7.17 Mocha failure as before.
New failure: CI Build - 7.17
New failure: CI Build - 7.17
Closing this as we don't have access to the FTR for 7.17 and we're only focusing on failing tests in main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - main
New failure: CI Build - 8.11
New failure: CI Build - 8.11
New failure: CI Build - 8.11
New failure: CI Build - 8.11
New failure: CI Build - 8.11
Closed for 8.11 by https://github.com/elastic/kibana/pull/170766
New failure: CI Build - 7.17
Looks like a CI environment issue:
Not prioritizing flaky tests for 7.17, so closing for now.
New failure: CI Build - main
New failure: CI Build - main
New failure: kibana-on-merge - 8.15
New failure: kibana-on-merge - main
A test failed on a tracked branch
First failure: CI Build - 7.17