Failing test: Plugin Functional Tests.test/plugin_functional/test_suites/core_plugins/logging·ts - core plugins plugin logging writes info_pattern context to custom pattern appender

[kibanamachine]

A test failed on a tracked branch

{ Error: expected [ '' ] to sort of equal [ 'CUSTOM - PATTERN [plugins.core_logging.info_pattern][INFO ] log2' ]
    at Assertion.assert (packages/kbn-expect/expect.js:100:11)
    at Assertion.eql (packages/kbn-expect/expect.js:244:8)
    at Context.it (test/plugin_functional/test_suites/core_plugins/logging.ts:119:53)
  actual: '[\n  ""\n]',
  expected:
   '[\n  "CUSTOM - PATTERN [plugins.core_logging.info_pattern][INFO ] log2"\n]',
  showDiff: true }

First failure: Jenkins Build

[elasticmachine]

Pinging @elastic/kibana-test-triage (failed-test)

[kibanamachine]

New failure: Jenkins Build

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[joshdover]

@restrry could this be fixed by #70168?

[mshustov]

@joshdover No, it seems to be a race condition problem.

[mshustov]

I suspect the problem exists because both console.log and write to stdout are async by nature. That's why I used spies in the integration tests

• https://github.com/elastic/kibana/blob/master/src/core/server/logging/integration_tests/logging.test.ts
• https://github.com/elastic/kibana/blob/master/src/core/server/legacy/integration_tests/logging.test.ts

Not sure if it would work out of the box for FTR tests, but it worth giving a try. Or we can move tests from functional tests with FTR to integration tests with jest as well.
Let me know if you don't have time, I can take a stab at it.

[kibanamachine]

New failure: Jenkins Build

[tylersmalley]

Failures over the past seven days:

Currently we're probably averaging a failure a day across PR's/branches which isn't a lot. But if it persists we will probably want to skip until it can be resolved.

[joshdover]

I'll try to move these to jest today, if it looks like it's going to take a lot of time, I'll merge a skip while I work out the details.