You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Mark Liu (JIRA)" <ji...@apache.org> on 2017/03/09 23:49:38 UTC

[jira] [Commented] (BEAM-1676) SdkCoreApiSurfaceTest Failed in JDK7&8 and OpenJDK7&8 on Jenkins

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

Mark Liu commented on BEAM-1676:
--------------------------------

two discovers from job logs:
1. failed version test uses matrixJob.steps.maven() to run maven command, instead of mavenJob() directly. After compared job logs, it looks like Jenkins uses different build mechanism to start maven job.
https://builds.apache.org/job/beam_PostCommit_Java_Version_Test/14/jdk=JDK%201.8%20(latest),label=beam/consoleFull
https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_MavenInstall/2847/consoleFull

2. Found this error right after maven command got executed:
/home/jenkins/tools/maven/apache-maven-3.3.3/bin/mvn: 200: local: 1.8: bad variable name
JDK 1.8 (latest) is used in "-Djdk=JDK 1.8 (latest)" and "-Dmaven.repo.local=/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Java_Version_Test/jdk/JDK 1.8 (latest)/label/beam/.repository" in execution command, which might be the reason causing test failure?

> SdkCoreApiSurfaceTest Failed in JDK7&8 and OpenJDK7&8 on Jenkins
> ----------------------------------------------------------------
>
>                 Key: BEAM-1676
>                 URL: https://issues.apache.org/jira/browse/BEAM-1676
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Mark Liu
>            Assignee: Davor Bonaci
>
> After running beam_PostCommit_Java_MavenInstall in different JDK versions (JDK7&8, OpenJDK7&8) on Jenkins, all failed due to following error:
> {code}
> Failed tests: 
>   SdkCoreApiSurfaceTest.testSdkApiSurface:59 
> Expected: API surface to include only:
> 	Classes in package "org.apache.beam"
> 	Classes in package "com.google.api.client"
> 	Classes in package "com.google.api.services.bigquery"
> 	Classes in package "com.google.api.services.cloudresourcemanager"
> 	Classes in package "com.google.api.services.pubsub"
> 	Classes in package "com.google.api.services.storage"
> 	Classes in package "com.google.auth"
> 	Classes in package "com.google.protobuf"
> 	Classes in package "com.fasterxml.jackson.annotation"
> 	Classes in package "com.fasterxml.jackson.core"
> 	Classes in package "com.fasterxml.jackson.databind"
> 	Classes in package "org.apache.avro"
> 	Classes in package "org.hamcrest"
> 	Classes in package "org.codehaus.jackson"
> 	Classes in package "org.joda.time"
> 	Classes in package "org.junit"
> 	
>      but: The following white-listed scopes did not have matching classes on the API surface:
> 	No Classes in package "com.fasterxml.jackson.annotation"
> 	No Classes in package "com.fasterxml.jackson.core"
> 	No Classes in package "com.fasterxml.jackson.databind"
> 	No Classes in package "com.google.api.client"
> 	No Classes in package "com.google.api.services.bigquery"
> 	No Classes in package "com.google.api.services.cloudresourcemanager"
> 	No Classes in package "com.google.api.services.pubsub"
> 	No Classes in package "com.google.api.services.storage"
> 	No Classes in package "com.google.auth"
> 	No Classes in package "com.google.protobuf"
> 	No Classes in package "org.apache.avro"
> 	No Classes in package "org.apache.beam"
> 	No Classes in package "org.codehaus.jackson"
> 	No Classes in package "org.hamcrest"
> 	No Classes in package "org.joda.time"
> 	No Classes in package "org.junit"
> {code}
> Job link:
> https://builds.apache.org/job/beam_PostCommit_Java_Version_Test/14/
> Multi-JDK version test is based on this PR:
> https://github.com/apache/beam/pull/2204/files
> Our beam_PostCommit_Java_MavenInstall is using JDK 1.8 (latest), which in good health. And the maven command in version test is the same as beam_PostCommit_Java_MavenInstall.
> Any ideas?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)