[
https://issues.apache.org/jira/browse/IGNITE-19738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-19738:
---------------------------------------
Description:
Everywhere in test, we should give up explicitly waiting of future completion
in favor of using matcher assert. This replacement is supposed to do for two
purpose:
# Limit of waiting time
# Throw exception with useful message
h3. Examples
{code:java}
{fut.joi(), fut.get(), fur.get(5, TimeUnit.SECONDS)} -> assertThat("Waiting
timeout of some particular future ran out", fut,
willCompleteSuccessfully()){code}
was:
Everywhere in test, we should give up explicitly waiting of future completion
in favor of using matcher assert. This replacement is supposed to do for two
purpose:
# Limit of waiting time
# Throw exception with useful message
h3. Examples
{_}{fut.joi(), fut.get(), fur.get(5, TimeUnit.SECONDS){_}} ->
_assertThat("Waiting timeout of some particular future ran out", fut,
willCompleteSuccessfully())_
> Replace fut.join() to assertThat(fut, willCompleteSuccessfully()) in all tests
> ------------------------------------------------------------------------------
>
> Key: IGNITE-19738
> URL: https://issues.apache.org/jira/browse/IGNITE-19738
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> Everywhere in test, we should give up explicitly waiting of future completion
> in favor of using matcher assert. This replacement is supposed to do for two
> purpose:
> # Limit of waiting time
> # Throw exception with useful message
> h3. Examples
> {code:java}
> {fut.joi(), fut.get(), fur.get(5, TimeUnit.SECONDS)} -> assertThat("Waiting
> timeout of some particular future ran out", fut,
> willCompleteSuccessfully()){code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
