[#150] scenarios: Use SelectorAwaiting for read and delete load in s3_dar.js, make delete_age optional
All checks were successful
DCO action / DCO (pull_request) Successful in 1m28s
Tests and linters / Tests (1.22) (pull_request) Successful in 3m14s
Tests and linters / Tests with -race (pull_request) Successful in 3m27s
Tests and linters / Tests (1.21) (pull_request) Successful in 3m40s
Tests and linters / Lint (pull_request) Successful in 4m29s

Signed-off-by: m.malygina <m.malygina@yadro.com>
This commit is contained in:
m.malygina 2024-06-21 15:52:57 +03:00
parent 0a9aeab47c
commit e7d4dd404a

View file

@ -86,7 +86,7 @@ const delete_age = __ENV.DELETE_AGE ? parseInt(__ENV.DELETE_AGE) : undefined;
let obj_to_delete_selector = undefined; let obj_to_delete_selector = undefined;
let obj_to_delete_exit_on_null = undefined; let obj_to_delete_exit_on_null = undefined;
if (registry_enabled && delete_age) { if (registry_enabled ) {
obj_to_delete_exit_on_null = (write_vu_count == 0) && (read_vu_count == 0) obj_to_delete_exit_on_null = (write_vu_count == 0) && (read_vu_count == 0)
let constructor = obj_to_delete_exit_on_null ? registry.getOneshotSelector let constructor = obj_to_delete_exit_on_null ? registry.getOneshotSelector