Travis Downs

> logging configuration error: Unknown logger 'seastar_memory'. Use --help-loggers to list available loggers. lol, oops, and no fair @dotnwat peeking at draft PRs ;). This arg definitely works locally for...

Oh, I see the problem is that this logger doesn't exist in _debug_ build because that build uses the libc allocator and the code that creates the `seastar_memory` logger object...

This change depends on: https://github.com/redpanda-data/seastar/pull/30

This change is ready for review, but needs this other change in vtools to be merged first to solve the debug build failure: https://github.com/redpanda-data/vtools/pull/869

> This needs a clustered ducktape run before merging to see which existing tests might be tripping bad_allocs routinely @jcsp - seems reasonable, is that something I can get CI...

I've rebased it and am working on a scale test run.

@jcsp - I ran this change on 7 x i3en.xlarge nodes: it passed 16/19 scale tests and the remaining three did not run because they required 12 nodes. I also...

Regarding the error string in the OP (newlines mine): ``` failure at 2022-07-31T11:04:20.402Z: NodeCrash([ (, "ERROR 2022-07-31 08:16:28,783 [shard 3] assert - Assert failure: (../../../src/v/storage/segment_reader.cc:215) '_parent == nullptr' Must close...

These test failures are legit: BadLogLines picks up the error messages for tests where we expect startup to fail, so I'll have to add these to the allowlist.

@dotnwat I've updated this with BadLogLines exclusions and it now passes everything.