You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/01/27 10:31:00 UTC
[jira] [Created] (IGNITE-18649) Tune default test timeouts
Roman Puchkovskiy created IGNITE-18649:
------------------------------------------
Summary: Tune default test timeouts
Key: IGNITE-18649
URL: https://issues.apache.org/jira/browse/IGNITE-18649
Project: Ignite
Issue Type: Improvement
Reporter: Roman Puchkovskiy
Assignee: Roman Puchkovskiy
Fix For: 3.0.0-beta2
It was found empirically (see IGNITE-18646) that a timeout of 1 minute (established in IGNITE-18638) is too small for some tests when they are run on our TC.
We need to do the following:
# Find good default timeouts which is not exceeded by most of unit/integration tests (it would be nice to have them close to 1 minute)
# Identify tests that have a risk of exceeding this timeout and set specific timeouts for them. For example, {{ItBplusTreeReuseListPersistentPageMemoryTest}} requires more than 1 minute; also, all JRaft timeouts should probably be more than 1 minute (to avoid changing tests themselves, we could put a junit-platform.properties in the corresponding module)
Tests in the corresponding branch need to be run a few times (maybe, 10-20 times) on TC to make sure the timeouts are adequate.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)