[jira] [Updated] (IGNITE-17048) Some failing tests make other tests fail too

["Aleksandr Polovtcev (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-17048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksandr Polovtcev updated IGNITE-17048:
-----------------------------------------
    Description: 
Looks like after some tests fail, they do not correctly free the used ports, because other tests start to fail with a "Failed to start the connection manager: No available port in range [3346-3346]" message.

Example of a failed build: https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunAllTests/6583070

A possible solution might be to create a diagnostics tool that will print the name of the process that occupies the blocked port.

  was:
Looks like after some tests fail, they do not correctly free the used ports, because other tests start to fail with a "Failed to start the connection manager: No available port in range [3346-3346]" message.

Example of a failed build: https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunAllTests/6583070


> Some failing tests make other tests fail too
> --------------------------------------------
>
>                 Key: IGNITE-17048
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17048
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>
> Looks like after some tests fail, they do not correctly free the used ports, because other tests start to fail with a "Failed to start the connection manager: No available port in range [3346-3346]" message.
> Example of a failed build: https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunAllTests/6583070
> A possible solution might be to create a diagnostics tool that will print the name of the process that occupies the blocked port.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)