You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mirza Aliev (Jira)" <ji...@apache.org> on 2022/01/21 10:53:00 UTC
[jira] [Updated] (IGNITE-16346) Test ConfigurationTest#testDirectAsyncContinuationExecutorUsesNettyThread is flaky
[ https://issues.apache.org/jira/browse/IGNITE-16346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mirza Aliev updated IGNITE-16346:
---------------------------------
Description:
Test {{ConfigurationTest#testDirectAsyncContinuationExecutorUsesNettyThread}} is flaky
https://ci.ignite.apache.org/test/463696443390860538?currentProjectId=ignite3_Test
{noformat}
java.lang.AssertionError:
Expected: a string starting with "nioEventLoopGroup-"
but: was "main"
Expected :a string starting with "nioEventLoopGroup-"
Actual :"main"
<Click to see difference>
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
at org.apache.ignite.client.ConfigurationTest.testDirectAsyncContinuationExecutorUsesNettyThread(ConfigurationTest.java:151)
{noformat}
Could be reproduced on {{main}} (87d5132b9) after app. 500 runs.
Possible root cause is that {{org.apache.ignite.table.manager.IgniteTables#tablesAsync}} future might be completed too early, so thread do not match to expected.
was:
Test {{ConfigurationTest#testDirectAsyncContinuationExecutorUsesNettyThread}} is flaky
https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunUnitTests/6379034?logFilter=debug
{noformat}
java.lang.AssertionError:
Expected: a string starting with "nioEventLoopGroup-"
but: was "main"
Expected :a string starting with "nioEventLoopGroup-"
Actual :"main"
<Click to see difference>
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
at org.apache.ignite.client.ConfigurationTest.testDirectAsyncContinuationExecutorUsesNettyThread(ConfigurationTest.java:151)
{noformat}
Could be reproduced on {{main}} (87d5132b9) after app. 500 runs.
Possible root cause is that {{org.apache.ignite.table.manager.IgniteTables#tablesAsync}} future might be completed too early, so thread do not match to expected.
> Test ConfigurationTest#testDirectAsyncContinuationExecutorUsesNettyThread is flaky
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-16346
> URL: https://issues.apache.org/jira/browse/IGNITE-16346
> Project: Ignite
> Issue Type: Bug
> Reporter: Mirza Aliev
> Priority: Blocker
> Labels: ignite-3
>
> Test {{ConfigurationTest#testDirectAsyncContinuationExecutorUsesNettyThread}} is flaky
> https://ci.ignite.apache.org/test/463696443390860538?currentProjectId=ignite3_Test
>
> {noformat}
> java.lang.AssertionError:
> Expected: a string starting with "nioEventLoopGroup-"
> but: was "main"
> Expected :a string starting with "nioEventLoopGroup-"
> Actual :"main"
> <Click to see difference>
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
> at org.apache.ignite.client.ConfigurationTest.testDirectAsyncContinuationExecutorUsesNettyThread(ConfigurationTest.java:151)
> {noformat}
> Could be reproduced on {{main}} (87d5132b9) after app. 500 runs.
> Possible root cause is that {{org.apache.ignite.table.manager.IgniteTables#tablesAsync}} future might be completed too early, so thread do not match to expected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)