tarantool / tarantool / 13194433510 / 1

88%

master: 88%

push

github

test: stabilize box-luatest/gh_8192_feedback_daemon_metrics test

The test failed sometimes in the following places:
NO_WRAP
```
 not ok 1	Feedback daemon metrics.test_metrics
 #   ...est/box-luatest/gh_8192_feedback_daemon_metrics_test.lua:69: Assertion failed: 89 < 60
 #   stack traceback:
 #   	...est/box-luatest/gh_8192_feedback_daemon_metrics_test.lua:69: in function <...est/box-luatest/gh_8192_feedback_daemon_metrics_test.lua:43>
 #   	...est/box-luatest/gh_8192_feedback_daemon_metrics_test.lua:43: in function 'Feedback daemon metrics.test_metrics'

 not ok 3	Feedback daemon metrics.test_metrics_no_collect
 #   ...est/box-luatest/gh_8192_feedback_daemon_metrics_test.lua:101: expected: nil, actual: {{1, 2}}
 #   stack traceback:
 #   	...est/box-luatest/gh_8192_feedback_daemon_metrics_test.lua:101: in function <...est/box-luatest/gh_8192_feedback_daemon_metrics_test.lua:92>
 #   	...est/box-luatest/gh_8192_feedback_daemon_metrics_test.lua:92: in function 'Feedback daemon metrics.test_metrics_no_collect'
```
NO_WRAP

The first case asserts that with a 0.01 second interval not more
than 60 metrics will be collected. Although under high load on the
runner, the number may go even higher than 400, meaning we've slept not
less than 4 seconds. So let's account elapsed time in the check.

The second case simply didn't clean any leftover metrics from
previous tests, and might fail if there are any.

NO_CHANGELOG=flaky test
NO_DOC=flaky test

(cherry picked from commit be2616241)

69705 of 123586 branches covered (56.4%)

102680 of 117533 relevant lines covered (87.36%)

2403905.01 hits per line