0

Everytime I launch tests with selenium, something like this appears in the console:

[5124:4344:1128/184821.088:ERROR:chrome_browser_main_extra_parts_metrics.cc(226)] crbug.com/1216328: Checking Bluetooth availability started. Please report if there is no report that this ends.
[5124:4344:1128/184821.145:ERROR:chrome_browser_main_extra_parts_metrics.cc(229)] crbug.com/1216328: Checking Bluetooth availability ended.
[5124:4344:1128/184821.195:ERROR:chrome_browser_main_extra_parts_metrics.cc(232)] crbug.com/1216328: Checking default browser status started. Please report if there is no report that this ends.
[5124:4344:1128/184821.289:ERROR:chrome_browser_main_extra_parts_metrics.cc(236)] crbug.com/1216328: Checking default browser status ended.

How can I disable it?

undetected Selenium
  • 183,867
  • 41
  • 278
  • 352
LazyBum Q
  • 257
  • 4
  • 12

1 Answers1

0

These error messages...

[5124:4344:1128/184821.088:ERROR:chrome_browser_main_extra_parts_metrics.cc(226)] crbug.com/1216328: Checking Bluetooth availability started. Please report if there is no report that this ends.
[5124:4344:1128/184821.145:ERROR:chrome_browser_main_extra_parts_metrics.cc(229)] crbug.com/1216328: Checking Bluetooth availability ended.

...are the result of some parametrized tests being flaky due to a timeout in recording expensive metrics on startup.

As per the discussion Parametrized tests are flaky due to a timeout in recording expensive metrics on startup isherman@chromium.org mentions either of the calls in chrome_browser_main_extra_parts_metrics.cc are flaky:

asvitkine@chromium.org in his commit mentioned:

Don't log histogram DefaultBrowser.State on Linux. The code to query the default browser state sometimes hangs Chrome start up on browser tests bots, causing flakiness. Disable the relevant code on Linux until a solution can be found. Also, revise some instrumentation messages to be more concise and more clear about when the bug in question might happen. Once this lands, we should be able to see if any more tests are affected by this or whether the bug can be closed and diagnostic logs can be removed.

This fix should address the issue in the upcoming releases once the flaky tests are addressed.

However, these log messages doesn't effects your tests and you can live with those.

undetected Selenium
  • 183,867
  • 41
  • 278
  • 352
  • For future reference: according to [GitLab](https://docs.gitlab.com/ee/development/testing_guide/flaky_tests.html), "[A flaky test] is a test that sometimes fails, but if you retry it enough times, it passes, eventually." By the way, it is 2022 and the same issue arises with the current version of Selenium. – Mew Feb 27 '22 at 19:47