[
https://issues.apache.org/jira/browse/IGNITE-28713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-28713:
---------------------------------------
Description:
Test LongRunningQueryTest.testQueryInitiatorId is flaky
(https://ci2.ignite.apache.org/viewLog.html?buildId=9083804).
Reason:
Test uses LONG_QUERY_WARNING_TIMEOUT as sleep parameters, in some rare cases
query execution can take exactly LONG_QUERY_WARNING_TIMEOUT time and in this
case query is not printed to log as "long running".
was:
Test LongRunningQueryTest.testQueryInitiatorId is flaky.
Reason:
Test uses LONG_QUERY_WARNING_TIMEOUT as sleep parameters, in some rare cases
query execution can take exactly LONG_QUERY_WARNING_TIMEOUT time and in this
case query is not printed to log as "long running".
> Flaky LongRunningQueryTest.testQueryInitiatorId
> -----------------------------------------------
>
> Key: IGNITE-28713
> URL: https://issues.apache.org/jira/browse/IGNITE-28713
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: MakeTeamcityGreenAgain, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Test LongRunningQueryTest.testQueryInitiatorId is flaky
> (https://ci2.ignite.apache.org/viewLog.html?buildId=9083804).
> Reason:
> Test uses LONG_QUERY_WARNING_TIMEOUT as sleep parameters, in some rare cases
> query execution can take exactly LONG_QUERY_WARNING_TIMEOUT time and in this
> case query is not printed to log as "long running".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
