[jira] [Commented] (IGNITE-17003) SqlDataTypesCoverageTests.testDecimalDataType failes flaky

["Ignite TC Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-17003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540153#comment-17540153 ] 

Ignite TC Bot commented on IGNITE-17003:
----------------------------------------

{panel:title=Branch: [pull/10027/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10027/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=6578257&buildTypeId=IgniteTests24Java8_RunAll]

> SqlDataTypesCoverageTests.testDecimalDataType failes flaky
> ----------------------------------------------------------
>
>                 Key: IGNITE-17003
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17003
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Taras Ledkov
>            Assignee: Taras Ledkov
>            Priority: Major
>             Fix For: 2.14
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a problem with this critical test - when start full test class there is high posibuility to get error on first tests. By default first test is testDecimalDataType. Every time I get different errors - it makes a suggestion about side effect of started cluster. Test doesn’t fail starting separately. 
> Case of fail: [atomicityMode=ATOMIC, cacheMode=PARTITIONED, ttlFactory=null, backups=2, evictionFactory=null, onheapCacheEnabled=false, writeSyncMode=FULL_ASYNC, persistenceEnabled=false]
> *Root cause:*
> The test is invalid for {{FULL_ASYNC }}mode. 
> The sequential execute
> UPDATE …
> SELECT …
> cannot guarantee visibility UPDATE changes for the SELECT query when FULL_ASYNC mode is used.
> *Possible fixes:*
> There can be two ways:
>     don’t use FULL_ASYNC mode at the test. 
>     wait for UPDATE changes is applied.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)