You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Wolfgang Knauf (Jira)" <ji...@apache.org> on 2025/02/08 15:22:00 UTC

[jira] [Updated] (SUREFIRE-2294) [regressiion] Debugging failsafe tests: Message "Listening for transport dt_socket at address" is written too late

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

Wolfgang Knauf updated SUREFIRE-2294:
-------------------------------------
    Summary: [regressiion] Debugging failsafe tests: Message "Listening for transport dt_socket at address" is written too late  (was: Debugging failsafe tests: Message "Listening for transport dt_socket at address" is written too late)

> [regressiion] Debugging failsafe tests: Message "Listening for transport dt_socket at address" is written too late
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-2294
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-2294
>             Project: Maven Surefire
>          Issue Type: Bug
>            Reporter: Wolfgang Knauf
>            Priority: Minor
>         Attachments: debug_test_mvn_listening_2222.png, debug_test_mvn_listening_352.png
>
>
> I launch integration tests with this command: "mvn -Pmyprofile -Dmaven.failsafe.debug verify"
> With 2.22.2, it prints a message "Listening for transport dt_socket at address: 5055" and then stops:
> !debug_test_mvn_listening_2222.png!
> With 3.5.2, it stops after the line "TESTS":
> !debug_test_mvn_listening_352.png!
>  
> The line "Listening for transport dt_socket at address: 5055" is written AFTER a debugger was attached. This is a bit too late, and it might confuse newbie users that don't know what is happening here and why it hangs.



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