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

Chris Nauroth updated HADOOP-19685:
-----------------------------------
    Fix Version/s: 3.5.0
                   3.4.3
     Hadoop Flags: Reviewed
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

> Clover breaks on double semicolon
> ---------------------------------
>
>                 Key: HADOOP-19685
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19685
>             Project: Hadoop Common
>          Issue Type: Task
>          Components: hadoop-aws
>    Affects Versions: 3.5.0, 3.4.2
>            Reporter: Michael Smith
>            Assignee: Michael Smith
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.5.0, 3.4.3
>
>
> Building with {{-Pclover}} fails with
> {code}
> [INFO] Instrumentation error
> com.atlassian.clover.api.CloverException: 
> /home/jenkins/hadoop/hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/impl/ITestS3APutIfMatchAndIfNoneMatch.java:43:43:unexpected
>  token: ;
> ...
> Failed to execute goal org.openclover:clover-maven-plugin:4.4.1:setup 
> (clover-setup) on project hadoop-aws: Clover has failed to instrument the 
> source files in the 
> [/home/jenkins/hadoop/hadoop-tools/hadoop-aws/target/clover/src-test-instrumented]
>  directory -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.openclover:clover-maven-plugin:4.4.1:setup (clover-setup) on project 
> hadoop-aws: Clover has failed to instrument the source files in the 
> [/home/jenkins/hadoop/hadoop-tools/hadoop-aws/target/clover/src-test-instrumented]
>  directory
> {code}
> It doesn't seem to like a double semicolon in 
> ITestS3APutIfMatchAndIfNoneMatch.java that was added in HADOOP-19256.



--
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