[QA][Code Coverage] exclude broken jest integration suites

[wayneseymour]

Summary

Excluding failing suites, after noticing they were breaking code coverage.
These jest integration suites dont allow the jest-integration portion to complete, so ingestion never starts.

Code Coverage Ingestion cannot start: #138426

[wayneseymour]

https://buildkite.com/elastic/kibana-code-coverage-main/builds/641

[wayneseymour]

https://buildkite.com/elastic/kibana-code-coverage-main/builds/645

[pgayvallet]

@wayneseymour could we get more details on that issue? I don't really like the idea of disabling some of our integration tests 'just' because there is an issue with the code coverage tool around them. Isn't there another way to address that problem?

[wayneseymour]

@wayneseymour could we get more details on that issue? I don't really like the idea of disabling some of our integration tests 'just' because there is an issue with the code coverage tool around them. Isn't there another way to address that problem?

Yeah I could understand that. From my perspective, it just "started happening".

IIRC, it happened right after this landed:
#136539

[wayneseymour]

@elasticmachine merge upstream

[wayneseymour]

running once more: https://buildkite.com/elastic/kibana-code-coverage-main/builds/665

[pgayvallet]

Seems green now?

[wayneseymour]

Seems green now?

kinda lol:

[wayneseymour]

@wayneseymour could we get more details on that issue? I don't really like the idea of disabling some of our integration tests 'just' because there is an issue with the code coverage tool around them. Isn't there another way to address that problem?

Fwiw, I concur with you about disabling them just because of cc.

[pgayvallet]

Problem should be addressed by #139636