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

Stamatis Zampetakis commented on HIVE-26332:
--------------------------------------------

The latest PR attempts to bump surefire to the latest surefire version (3.2.5) 
as of now. However, there were a lots of failures in the post-processing phase 
of the tests due to a behavior change that came with SUREFIRE-1744. The 
standard output is now part of the XML report by default and this causes 
xmlstarlet to choke [when attempting to 
process|https://github.com/apache/hive/blob/0f8190fefa56513a042566ef87b852e8343610aa/Jenkinsfile#L373]
 these (now) huge XML files. A sample error is outlined below.

{noformat}
./standalone-metastore/metastore-server/target/surefire-reports/TEST-org.apache.hadoop.hive.metastore.client.TestDatabases.xml:58725.7:
 internal error: Huge input lookup
[DEBUG] 2024-02-02 15:04:58.537 [main] Query - JDOQL Query : Compile (datastore)
{noformat}

Another side effect from not being able to process the results (and remove 
stdout/stderr) is that the resulting test report is huge ~1GB (zipped). Since 
CI Jenkins builds for PR are retained this further means that PR with similar 
failures are a significant burden for Jenkins and the CI infra.

> Upgrade maven-surefire-plugin to 3.2.5
> --------------------------------------
>
>                 Key: HIVE-26332
>                 URL: https://issues.apache.org/jira/browse/HIVE-26332
>             Project: Hive
>          Issue Type: Task
>          Components: Testing Infrastructure
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Currently we use 3.0.0-M4 which was released in 2019. Since there have been 
> multiple bug fixes and improvements.
> Worth mentioning that interaction with JUnit5 is much more mature as well and 
> this is one of the main reasons driving this upgrade.



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

Reply via email to