Open kibanamachine opened 3 years ago
New failure: Jenkins Build
Pinging @elastic/apm-ui (Team:apm)
Started failing a lot all of the sudden, skipping
Skipped
master/8.0: https://github.com/elastic/kibana/commit/562c3cc67c99993664711817cd9ac86d748ed245 + https://github.com/elastic/kibana/commit/c43429c13b6994a091b69651009dd6bc5ece5709 7.x/7.16: https://github.com/elastic/kibana/commit/91bf123af041ff002d2234cc964eff4e2163ff7a + https://github.com/elastic/kibana/commit/bcbe434c0e3d1ee65c0b3f1f33a94d6e9d9129ac
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
New failure: Jenkins Build
Even after skip this continues to fail so I've skipped both the x-pack/test/rule_registry/security_and_spaces/config_basic.ts
and x-pack/test/rule_registry/security_and_spaces/config_trial.ts
configs.
Pinging @elastic/security-solution (Team: SecuritySolution)
Pinging @elastic/security-threat-hunting (Team:Threat Hunting)
Pinging @elastic/security-detections-response (Team:Detections and Resp)
Closing since the test has been unskipped.
Just saw 2 comments about this ticket in the code:
@MadameSheema Should this ticket be reopened?
Absolutely @maryam-saeidi thanks for the info!!
@yctercero can you please take a look when you have the chance? Thanks!
This would be the RAC team now - @elastic/response-ops
A test failed on a tracked branch
First failure: Jenkins Build