Piotr Smaron

All comments have been addressed, the one remaining https://github.com/scylladb/scylladb/issues/20566 will be done as a follow up in a separate PR @scylladb/scylla-maint can you please review/queue? The CI is green.

@scylladb/scylla-maint please consider reviewing/merging.

@KrzaQ can you post your summary? As far as I recall, you couldn't reproduce the issue, so now we're just waiting for it to reappear to have some additional data...

@KrzaQ once you're back on analyzing this issue, please save the logs from the failed testcase run (attach to the comment), so they don't disappear.

> @KrzaQ can you post your summary? As far as I recall, you couldn't reproduce the issue, so now we're just waiting for it to reappear to have some additional...

I took a look again, and don't know what's happening, perhaps @nyh could help here. I was tracking down logs of create table events. [Node1 logs](https://jenkins.scylladb.com/job/enterprise-2024.1/job/dtest-debug/46/artifact/logs-full.debug.028/1727557939845_alternator_tests.py%3A%3ATesterAlternator%3A%3Atest_slow_query_logging/node1.log): ``` INFO 2024-09-28 21:00:14,908...

Thanks @nyh @fruch we're stuck and need your help, could you please take a look at this issue? Especially the comments by @nyh made [here](https://github.com/scylladb/scylladb/issues/15456#issuecomment-1763475406).

Can we close this issue? If the failure appears again, we can reopen it.

I don't see any new GH issues opened against the reported flaky test, closing for the time being and keeping fingers crossed that @fruch 's https://github.com/scylladb/scylladb/issues/15456#issuecomment-2456740928 made the issue go...

> I thought we were randomizing the names? @mykaul yes, but we weren't exactly sure if it's going to help.