EACL tests take too much time #309

Closed
opened 2025-12-28 18:15:49 +00:00 by sami · 0 comments
Owner

Originally created by @roman-khimov on GitHub (Sep 24, 2024).

Current Behavior

test_extended_acl_numeric_values --- each takes 3m30s to run.
test_extended_acl_numeric_values_attr_str_filter_numeric --- 30s
test_extended_acl_numeric_values_payload_attr --- 30s

https://rest.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/544-1727128149/index.html#suites/7d0d2bff4573ced7a233aef01d2141a2/b20b4234dc3e1081/

Expected Behavior

EACL is managed via blockchain transactions, but the chain we have in test environment has 1s blocks, so it does not take 15-30s to update anything there. I'd bet there is some excessive waiting in the test.

Possible Solution

Try to optimize it.

Originally created by @roman-khimov on GitHub (Sep 24, 2024). ## Current Behavior test_extended_acl_numeric_values --- each takes 3m30s to run. test_extended_acl_numeric_values_attr_str_filter_numeric --- 30s test_extended_acl_numeric_values_payload_attr --- 30s https://rest.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/544-1727128149/index.html#suites/7d0d2bff4573ced7a233aef01d2141a2/b20b4234dc3e1081/ ## Expected Behavior EACL is managed via blockchain transactions, but the chain we have in test environment has 1s blocks, so it does not take 15-30s to update anything there. I'd bet there is some excessive waiting in the test. ## Possible Solution Try to optimize it.
sami 2025-12-28 18:15:49 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-testcases#309
No description provided.