psutils_linux_clean_info.test_clean_thread_info is a test that sometimes failed on CI runs, see [1] for example. You cannot guarantee that the quantity of coio threads would be bigger for {worker_pool_threads = 100} rather than {worker_pool_threads = 1}, since it defines only the upper threshold. The new version of the test checks that there are at least three threads in metrics (after box.cfg{}, there should be at least tx, iproto and wal) and each thread has system and user time metrics.
psutils_linux_clean_info.test_clean_thread_info
is a test that sometimes failed on CI runs, see [1] for example. You cannot guarantee that the quantity ofcoio
threads would be bigger for{worker_pool_threads = 100}
rather than{worker_pool_threads = 1}
, since it defines only the upper threshold. The new version of the test checks that there are at least three threads in metrics (afterbox.cfg{}
, there should be at leasttx
,iproto
andwal
) and each thread has system and user time metrics.I didn't forget about
Part of tarantool/tarantool#7725