[FTR] Disable dockerServers service when stubbing

[dgieselaar]

Currently the dockerServers service starts a package registry container even if there are no tests. The package registry container can take up to 2m to start on CI, so it adds an unnecessary delay.

Relates to: #237584

[dmlemeshko]

@dgieselaar I skipped tests to reproduce the issue, but I couldn't in main. Do you have config where it actually starts containers during tests check?

*[main][~/github/kibana]$ node scripts/functional_tests.js --config x-pack/solutions/observability/test/serverless/functional/configs/config.ts
 warn ❗️❗️❗️
 warn ❗️❗️❗️
 warn ❗️❗️❗️
 warn    Don't forget to use `node scripts/build_kibana_platform_plugins` to build plugins you plan on testing
 warn ❗️❗️❗️
 warn ❗️❗️❗️
 warn ❗️❗️❗️
 info Filtering out any suites that include the tag(s): [ 'skipSvlOblt' ]
 info Filtering out any suites that include the tag(s): [ 'skipSvlOblt' ]
 info Filtering out any suites that include the tag(s): [ 'skipSvlOblt' ]
 info Starting tests

 └-: serverless observability UI
   └-> "before all" hook: beforeTestSuite.trigger in "serverless observability UI"
   └-: navigation
     └-> "before all" hook: beforeTestSuite.trigger for "navigate observability sidenav & breadcrumbs"
     └-> "before all" hook for "navigate observability sidenav & breadcrumbs"
     └-> navigate observability sidenav & breadcrumbs
     └-> active sidenav section is auto opened on load
     └-> shows cases in sidebar navigation
     └-> navigates to cases app
     └-> navigates to alerts app

0 passing (1ms)
5 pending

The code change makes sense, just want to see the actual issue.

[dgieselaar]

@dmlemeshko yes, locally you have to specify FLEET_PACKAGE_REGISTRY_PORT=6064 to have it start the container. But there are plenty of examples. If you go to https://buildkite.com/elastic/kibana-pull-request/builds/349260/steps/canvas?sid=0199c918-953f-4f51-b2ea-f6c70e3325e1, collapse the groups and search for configs containing serverless at the bottom you'll see a couple of examples.

[dmlemeshko]

LGTM

[dgieselaar]

I'm waiting until #238397 is in so I can get evidence of this being an improvement.

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 885959d

Failed CI Steps

• FTR Configs #64
• FTR Configs #122

Test Failures

• [job] [logs] FTR Configs #122 / lens serverless - group 1 - subgroup 6 lens logsdb smoke testing functions support Scenarios with changing stream type LogsDB downgraded to regular data stream scenarios LogsDB stream with no additional stream/index and no host.name field should visualize a date histogram chart
• [job] [logs] FTR Configs #64 / serverless security UI Serverless Security Cases Cases List bulk actions severity change the severity of cases to medium correctly

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
@kbn/test	309	310	+1

Unknown metric groups

API count

id	before	after	diff
@kbn/test	366	367	+1

History

• 💛 Build #349626 was flaky 9c93b7f
• 💚 Build #348577 succeeded 715ff69
• 💚 Build #348132 succeeded 038b44d
• 💔 Build #347867 failed 088f192
• 💔 Build #347677 failed 9d44877

cc @dgieselaar

[dgieselaar]

Based on the following query I think there's about 8 configs that were starting docker even without tests:

FROM scout-test-events-*
  | WHERE reporter.type == "ftr" AND buildkite.build.number IN (350861, 350741) AND event.action == "run-end"
  | WHERE test_run.tests.total == 0
  | SORT process.uptime DESC
  | STATS left = AVG(process.uptime) WHERE buildkite.build.number == 350861, right = AVG(process.uptime) WHERE buildkite.build.number != 350861 BY test_run.config.file.path
  | SORT right DESC

So this saves about 10m tops. Not much, but it's a sane thing to do.

[kibanamachine]

Starting backport for target branches: 9.2

https://github.com/elastic/kibana/actions/runs/18504791591

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	9.2

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation