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

ASF GitHub Bot commented on HADOOP-19964:
-----------------------------------------

joseluisll commented on code in PR #8682:
URL: https://github.com/apache/hadoop/pull/8682#discussion_r3813797753


##########
hadoop-common-project/hadoop-common/pom.xml:
##########
@@ -541,12 +541,6 @@
           <systemPropertyVariables>
             <runningWithNative>${runningWithNative}</runningWithNative>
           </systemPropertyVariables>
-          <properties>
-            <property>
-              <name>listener</name>
-              <value>org.apache.hadoop.test.TimedOutTestsListener</value>

Review Comment:
   Taken your route. The META-INF/services descriptor is gone and the listener 
property stays in all eight poms — the PR now touches no pom at all.
   
   TimedOutTestsListener implements TestExecutionListener, so the wiring 
already in the tree starts working on a Surefire bump alone once 
apache/maven-surefire#3438 lands. Dormant until then, which the description now 
says; the dump Hadoop's tests get today comes from waitFor calling 
dumpForTimeout directly, which needs no registration.





> Restore TimedOutTestsListener thread dumps on test timeout
> ----------------------------------------------------------
>
>                 Key: HADOOP-19964
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19964
>             Project: Hadoop Common
>          Issue Type: Test
>            Reporter: Jose Luis López
>            Priority: Critical
>              Labels: pull-request-available
>
> Goal: a test that fails on @Timeout prints a full thread dump into its
> surefire report. Today it prints nothing, and a timeout without thread state
> is undiagnosable after the fact.
>  
> This is a regression. TimedOutTestsListener (HADOOP-8755, 2012) did exactly
> this until the JUnit 5 migration (HADOOP-19415 Part4) left it implementing no
> listener interface. The Surefire "listener" property that 8 poms still carry
> registers nothing.
>  
> Fix:
> * Reimplement it as a JUnit Platform TestExecutionListener, auto-registered
> via META-INF/services in the hadoop-common test artifact.
> * Remove the dead "listener" property from the 8 poms.
> * -Dhadoop.test.timedout.dump=false turns it off;
> -Dhadoop.test.timedout.dump.limit (default 5) caps dumps per JVM.
>  
> Covers timeouts that fail through JUnit. Does not cover Surefire's fork kill
> (forkedProcessTimeoutInSeconds), which halts the JVM and bypasses listeners.
> Complements HADOOP-19950, whose CI upload globs already capture the report
> files these dumps land in.
>  
> The listener activates for every consumer of the hadoop-common test artifact,
> including HBase, Ozone, Hive and Tez: needs a release note.
>  
> Test-scope only; no production code is touched.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to