[
https://issues.apache.org/jira/browse/IGNITE-27755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18056818#comment-18056818
]
Ignite TC Bot commented on IGNITE-27755:
----------------------------------------
{panel:title=Branch: [pull/12701/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12701/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8844169&buildTypeId=IgniteTests24Java8_RunAll]
> Flaky SqlDiagnosticIntegrationTest
> ----------------------------------
>
> Key: IGNITE-27755
> URL: https://issues.apache.org/jira/browse/IGNITE-27755
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: calcite, ise
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Tests {{testSqlFieldsQueryWithInitiatorId}} and {{testSqlQueryTotalDuration}}
> are flaky.
> Reason:
> * {{testSqlFieldsQueryWithInitiatorId}} uses {{LONG_QRY_TIMEOUT}} as sleep
> parameters, in some rare cases query execution can take exactly
> {{LONG_QRY_TIMEOUT}} time and in this case query is not printed to log as
> "long running".
> * {{testSqlQueryTotalDuration}} starts async thread with query, but this
> async thread can delay a little bit and total query duration can be
> calculated wrongly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
