[
https://issues.apache.org/jira/browse/IGNITE-28686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Pavlov updated IGNITE-28686:
-----------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> .NET: Improve diagnostics and timeout in DeploymentTest.TestCustomDeployment
> ----------------------------------------------------------------------------
>
> Key: IGNITE-28686
> URL: https://issues.apache.org/jira/browse/IGNITE-28686
> Project: Ignite
> Issue Type: Task
> Reporter: Ignite TC Bot
> Priority: Major
> Labels: MakeTeamcityGreenAgain, ignite-2, ise
> Attachments: ai-prompt (3).txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Platform .NET (Windows) TeamCity build consistently reports
> Apache.Ignite.Core.Tests.DeploymentTest.TestCustomDeployment as failed after
> ~35s, often with empty failure details.
> Observed signal:
> * Suite: IgniteTests24Java8_PlatformNetWindows
> * Builds: 9066660 and repeated recent runs
> * Test: Apache.Ignite.Core.Tests.DeploymentTest.TestCustomDeployment
> * Duration: ~34-36s
> Investigation:
> The test starts a custom-deployed Apache.Ignite.exe process, does only a
> 300ms early-exit check, then starts an in-process node and waits for topology
> size 2 with the default 30s timeout. If the external process is slow on
> Windows CI, or exits after the initial 300ms window, the failing assertion
> does not include the child process stdout/stderr, making TeamCity failure
> details unhelpful.
> Proposed minimal test fix:
> * Increase the topology wait only for this custom external-node deployment
> path.
> * Include external process state, exit code, and captured output in assertion
> messages.
> Local validation:
> * git diff --check passes.
> * Full .NET test could not be run in the investigation environment because
> dotnet/msbuild are unavailable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
