John Spray

> It seems that the current status is not very nice for community build:(. Tried to build many branches and versions, but still struggle to get a successful build. You...

To summarize the state of things: - toolchain images on dockerhub are badly out of date, avoid them - install-dependencies.sh is relying on your distro's clang/llvm version, and if that...

Here it is on dedicated EC2 instances where there shouldn't be a lot of background noise: FAIL test: ConnectionRateLimitTest.connection_rate_test (1/2 runs) failure at 2022-08-01T10:40:48.978Z: AssertionError('Time for first iteration:2.0255379676818848 Time for...

@dotnwat I haven't dug into the logs, but is this something ever expected under normal circumstances?

Another badloglines example https://buildkite.com/redpanda/redpanda/builds/13171#01823ef7-8a0f-4c14-b1e5-942de9800afe ``` rptest.services.utils.BadLogLines: ```

In general I like to have different failure modes in different tickets, but in the case of a brand new test that's failing several ways, I think it makes sense...

Hmm, the silent catches are mostly for shutdown exceptions that are definitely not indicative of an issue. This seems more like something that happens when the system isn't progressing well:...

Considering blocking this on https://github.com/vectorizedio/redpanda/issues/2376 (make test runners use faster storage) -- any tests that hit the disk will become significantly less deterministic when they're all competing for the same...

> Is this fundamentally difficult to achieve (e.g. because of clashes in net/fs/ipc namespaces)? No, but the tests need some shepherding to make it work. There are tests (not unit...

Similar failure on the same test, on a different group API FAIL test: PartitionMovementUpgradeTest.test_basic_upgrade (7/37 runs) failure at 2022-08-05T07:30:11.541Z: in job https://buildkite.com/redpanda/redpanda/builds/13658#01826c85-9f41-44eb-9564-83cc5724d06e