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

CI Failure (Oversized Alloc) in LargeControllerSnapshotTest.test_join_restart #16323

Closed
vbotbuildovich opened this issue Jan 27, 2024 · 1 comment
Labels
auto-triaged used to know which issues have been opened from a CI job ci-failure

Comments

@vbotbuildovich
Copy link
Collaborator

https://buildkite.com/redpanda/vtools/builds/11612

Module: rptest.scale_tests.large_controller_snapshot_test
Class: LargeControllerSnapshotTest
Method: test_join_restart
test_id:    LargeControllerSnapshotTest.test_join_restart
status:     FAIL
run time:   347.560 seconds

<BadLogLines nodes=ip-172-31-41-57(4),ip-172-31-32-94(4),ip-172-31-36-93(4) example="WARN  2024-01-25 21:32:46,770 [shard 0:main] seastar_memory - oversized allocation: 593920 bytes. This is non-fatal, but could lead to latency and/or fragmentation issues. Please report: at 0x77d1abb 0x74dc503 0x74e7e9b 0x34bdc07 0x70928a3 0x709285f 0x706a0e7 0x707be03 0x707c3e3 0x75880c3 0x758a777 0x758894b 0x74af69f 0x74ae1f3 0x2cc9f47 0x7d88307 /opt/redpanda/lib/libc.so.6+0x2b1c7 /opt/redpanda/lib/libc.so.6+0x2b29f 0x2cc366f">
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 184, in _do_run
    data = self.run_test()
  File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 269, in run_test
    return self.test_context.function(self.test)
  File "/home/ubuntu/redpanda/tests/rptest/services/cluster.py", line 142, in wrapped
    redpanda.raise_on_bad_logs(
  File "/home/ubuntu/redpanda/tests/rptest/services/redpanda.py", line 1365, in raise_on_bad_logs
    raise BadLogLines(bad_lines)
rptest.services.utils.BadLogLines: <BadLogLines nodes=ip-172-31-41-57(4),ip-172-31-32-94(4),ip-172-31-36-93(4) example="WARN  2024-01-25 21:32:46,770 [shard 0:main] seastar_memory - oversized allocation: 593920 bytes. This is non-fatal, but could lead to latency and/or fragmentation issues. Please report: at 0x77d1abb 0x74dc503 0x74e7e9b 0x34bdc07 0x70928a3 0x709285f 0x706a0e7 0x707be03 0x707c3e3 0x75880c3 0x758a777 0x758894b 0x74af69f 0x74ae1f3 0x2cc9f47 0x7d88307 /opt/redpanda/lib/libc.so.6+0x2b1c7 /opt/redpanda/lib/libc.so.6+0x2b29f 0x2cc366f">
@vbotbuildovich vbotbuildovich added auto-triaged used to know which issues have been opened from a CI job ci-failure labels Jan 27, 2024
@rockwotj rockwotj changed the title CI Failure (key symptom) in LargeControllerSnapshotTest.test_join_restart CI Failure (Oversized Alloc) in LargeControllerSnapshotTest.test_join_restart Jan 30, 2024
@rockwotj
Copy link
Contributor

Duplicate of #16320

@rockwotj rockwotj marked this as a duplicate of #16320 Jan 30, 2024
@rockwotj rockwotj closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-triaged used to know which issues have been opened from a CI job ci-failure
Projects
None yet
Development

No branches or pull requests

2 participants