[
https://issues.apache.org/jira/browse/IGNITE-29002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107787#comment-18107787
]
Ignite TC Bot commented on IGNITE-29002:
----------------------------------------
{panel:title=Branch: [pull/13508/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13508/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=9302759&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9302759
rerunBuildIds=none{color}
> VerifyBackupPartitionsTask should not use test-only executor
> ------------------------------------------------------------
>
> Key: IGNITE-29002
> URL: https://issues.apache.org/jira/browse/IGNITE-29002
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladimir Steshin
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> `{_}VerifyBackupPartitionsTask{_}` should not use:
> {code:java}
> /** Only for tests. Overrides the default pool. */
> @TestOnly
> public static volatile ExecutorService EXECUTOR_SERVICE; {code}
> [Attempt to
> fix|https://github.com/apache/ignite/pull/13494/changes/e79362f6fcd91367495b05d88f2dc2a12f5c86c0#diff-00647133d8d7a880859c81849f77a1604d2a9193d557f6b3b96dcf6685bb6324]
> But is flaky. Sometimes, idle verify is just able to finish. Probably, we do
> not wait its start before asking `beforeCancelLatch`
> {code:java}
> IgniteInternalFuture<Integer> idleVerifyFut = GridTestUtils.runAsync(() -> {
> if (checkCrc)
> execute("--cache", "idle_verify", "--check-crc");
> else
> execute("--cache", "idle_verify");
> });
> assertTrue(beforeCancelLatch.await(getTestTimeout(), TimeUnit.MILLISECONDS));
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
