Dmitriy Kruglov
Dmitriy Kruglov
> Is there a reason for doing it in the commit that moves tests, instead of doing it that way from the beginning? There was a bit of mess in...
> Two things: It was OK, but due to this number of nit related changes one of recent rebases went wrong. Will correct it
> > Two things: > > It was OK, but due to this number of nit related changes one of recent rebases went wrong. Will correct it @Lorak-mmk This time...
> https://jenkins.scylladb.com/view/master/job/scylla-master/job/kafka_connectors/ , but speak with @dimakr as recently new tests were added but I think we miss still jenkins jobs for it. Right, we have jobs for kafka source...
Another occurrence of the issue, which introduced false positive in the test result during [longevity-schema-topology-changes-12h-test](https://argus.scylladb.com/test/e0d56457-6e58-49db-9f1e-ab59bfeab88a/runs?additionalRuns[]=a507ebff-0f45-4dd0-85a8-a0ac714c9bae). The test issues `nodetool rebuild` command during AddRemoveDc Nemesis and then waits for `rebuild.*started` kind...
> maybe we could introduce `scylla_logger_settings` param? This should be appendable to `append_scylla_args` Appendability of additional parameters, which this change adds, is a needed thing indeed. But for customizing scylla...
Still reproduced with s-b v0.2.2 as described in https://github.com/scylladb/scylla-cluster-tests/pull/10698#issuecomment-2830105214
Seeing the same `storage_proxy - exception during mutation write...data_dictionary::no_such_column_family` error, which is accompanied with the `Error applying view update` one ([longevity-multidc-schema-topology-changes-12h-test](https://argus.scylladb.com/test/8764d79e-d785-4b99-9c70-99e2f24d0a18/runs?additionalRuns[]=108e1443-8a34-4e76-a32b-4a58b1e9bec8)): ``` < t:2024-08-30 15:22:59,937 f:db_log_reader.py l:123 c:sdcm.db_log_reader p:DEBUG >...
@fruch draft for the https://github.com/scylladb/qa-tasks/issues/1761 task implementation. Do you think it is something we can continue with? I tried some other options, but they are messy. This one is readable,...
> I'd propose making it automatic: create a decorator that will: > > 1. write to a file info about given function that is completed (e.g line in e.g. /tmp/completed-steps-...