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

memory-sampling: Reduce reactor count for mem sampling tests #11518

Conversation

StephanDollberg
Copy link
Member

In those tests we set a std::stringstream for the seastar logger so that
we can actually test what is being logged.

However, in contrast to std::cerr std::stringstream is of course not
threadsafe so if multiple reactors try to log at the same time things go
wrong.

Ideally we could just use <syncstream> but libc++ doesn't support that
yet. Hence, just run the tests with only a single reactor thread.

Additionally properly stop the services.

Issue #11513

Backports Required

  • none - not a bug fix
  • none - this is a backport
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v23.1.x
  • v22.3.x
  • v22.2.x

Release Notes

  • none

In those tests we set a `std::stringstream` for the seastar logger so that
we can actually test what is being logged.

However, in contrast to `std::cerr` `std::stringstream` is of course not
threadsafe so if multiple reactors try to log at the same time things go
wrong.

Ideally we could just use `<syncstream>` but libc++ doesn't support that
yet. Hence, just run the tests with only a single reactor thread.

Additionally properly stop the services.

Issue redpanda-data#11513
@mmaslankaprv mmaslankaprv self-requested a review June 19, 2023 14:14
@mmaslankaprv mmaslankaprv merged commit 6229f61 into redpanda-data:dev Jun 19, 2023
@StephanDollberg StephanDollberg deleted the stephandollberg/mem-sampling-logger-tests branch June 19, 2023 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants