Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test_metric_collection is flaky #4354

Closed
koivunej opened this issue May 26, 2023 · 1 comment
Closed

test_metric_collection is flaky #4354

koivunej opened this issue May 26, 2023 · 1 comment
Labels
a/test/flaky Area: related to flaky tests a/test Area: related to testing

Comments

@koivunej
Copy link
Member

Unlike previous #3186 now we have an assertion like:

test_runner/regress/test_metric_collection.py:167: in test_metric_collection
    assert len(metric_kinds_checked) == len(
E   AssertionError: Expected to receive and check all kind of metrics, but {'written_size', 'remote_storage_size', 'resident_size', 'timeline_logical_size'} got uncovered
E   assert 0 == 4
E    +  where 0 = len(set())
E    +  and   4 = len({'remote_storage_size': <function <lambda> at 0x7fa57e584b80>, 'resident_size': <function <lambda> at 0x7fa57e584af0>, 'timeline_logical_size': <function <lambda> at 0x7fa57e584c10>, 'written_size': <function <lambda> at 0x7fa57e584a60>})

I guess is that means that we never upload those metrics. Previous issue had only written_size.

Example allure report with failures:

  • pg14 + noop
  • pg15 + noop
  • pg15 + local_fs

I feel like we've seen this more broadly than the above.

@koivunej koivunej added a/test Area: related to testing a/test/flaky Area: related to flaky tests labels May 26, 2023
@koivunej
Copy link
Member Author

It seems #4346 should had already fixed this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/test/flaky Area: related to flaky tests a/test Area: related to testing
Projects
None yet
Development

No branches or pull requests

1 participant