Artsiom Mishuta

@fruch, It looks like a bug in the code. But I'm guessing that this was deleted because the scan can be too big. And we are just getting command responses...

> @mykaul @temichus what does `tests/longevity-tier1` mean exactly? There is a simple workaround as @aleksbykov wrote in the original report Impact section: > > > not critical and as workaround...

> @temichus please update the nemesis, scylladb works as expected here (thanks to ip addresses being managed by gossip @kbr-scylla) put in our backlog

> > SCT tier1 tests > > What are tier1 tests and how are they different from tierX or non-tier1 tests? Are they more important than other tests? > >...

> @temichus if you want to apply workaround (it should be simple), I think a separate issue would be appropriate in this case (maybe in SCT repo) created separate issue...

@fruch could you please leave some comments together with reassigning issues to my team?

@kostja @nyh could you please clarify random-seed in boost tests it is just "Random number generator seed" correct? " python equivalent for this is https://docs.python.org/3/library/random.html#random.seed pytest-randomly is pytest plugin that...

@nyh can you point me to where/how we install pytest-randomly and where we are using it? because it is not registered in pytest by default in ```./tools/toolchain/dbuild```? ``` setuptools registered...

probably yes. because toolchain is official environment where test.py should be run. And it does not have --randomly-seed option So, @kostja could you please clarify your request?

> pytest-randomly is used in test_random_failures.py > > We can split this issue into two: > > * remove pytest-randomly from test_random_failures test_random_failures.py - are not used pytest-randomly it uses...