[jira] [Commented] (IGNITE-17937) [Extensions] Confusing folder appears after running Ignite Extension tests.

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

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

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

{panel:title=Branch: [pull/10334/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10334/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=6852336&buildTypeId=IgniteTests24Java8_RunAll]

> [Extensions] Confusing folder appears after running Ignite Extension tests.
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-17937
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17937
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Mikhail Petrov
>            Assignee: Mikhail Petrov
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Confusing folder with name sys:IGNITE_HOME appears after running Ignite Extension tests.
> It happens because GridTestUtils#initTestProjectHome method which is responsible for initializing IGNITE_HOME system property for non Ignite tests does not work corrctly.
> First invocation of U.getIgniteHome() method tries to resolve Ignite Home path and in case of a failure initializes it with null.
> U.setIgniteHome(...) does actually nothing if the previous attempt to resolve Ignite Home was performed (even if it fails and null was set).



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