You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2026/10/10 12:29:00 UTC

[jira] [Commented] (IGNITE-29132) Fix flaky TaskNameResolutionTest

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

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

{panel:title=Branch: [pull/13680/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13680/head] Base: [master] : New Tests (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Cache 13{color} [[tests 1|https://ci2.ignite.apache.org/viewLog.html?buildId=9401792]]
* {color:#013220}IgniteCacheTestSuite13: SystemViewCacheExpiryPolicyTest.testCacheViewExpiryPolicy[factory=javax.cache.configuration.FactoryBuilder$SingletonFactory@418f890f, actual=SingletonFactory [expiryPlc=EternalExpiryPolicy [create=ETERNAL]]] - PASSED{color}

{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9401928&amp;buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9401928 rerunBuildIds=9403503,9403505,9403507,9403509{color}

> Fix flaky TaskNameResolutionTest
> --------------------------------
>
>                 Key: IGNITE-29132
>                 URL: https://issues.apache.org/jira/browse/IGNITE-29132
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Nikita Amelchev
>            Assignee: Nikita Amelchev
>            Priority: Minor
>             Fix For: 2.19
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The test fails with NPE in {{GridTaskProcessor.saveTaskMetadata}} on a task started right after the cluster activation. The task name cache is set by the activation callback, which runs asynchronously after the cluster state change completes, so the field is still empty for a moment.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)