Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[metro-dev] Build failed in Jenkins: WS Test Harness master build #24

See <https://ci.eclipse.org/metro/job/ws-test-harness-master-build/24/display/redirect?page=changes>

Changes:

[Lukas Jungmann] Bump ant from 1.10.7 to 1.10.9


------------------------------------------
[...truncated 1.44 KB...]
    name: "jnlp"
    resources:
      limits:
        memory: "4096Mi"
        cpu: "2000m"
      requests:
        memory: "4096Mi"
        cpu: "1000m"
    securityContext:
      privileged: false
    tty: true
    volumeMounts:
    - mountPath: "/home/jenkins/.m2/toolchains.xml"
      name: "m2-dir"
      readOnly: true
      subPath: "toolchains.xml"
    - mountPath: "/home/jenkins/.mavenrc"
      name: "m2-dir"
      readOnly: true
      subPath: ".mavenrc"
    - mountPath: "/opt/tools"
      name: "volume-0"
      readOnly: false
    - mountPath: "/home/jenkins"
      name: "volume-2"
      readOnly: false
    - mountPath: "/home/jenkins/.m2/repository"
      name: "volume-3"
      readOnly: false
    - mountPath: "/home/jenkins/.m2/settings-security.xml"
      name: "m2-secret-dir"
      readOnly: true
      subPath: "settings-security.xml"
    - mountPath: "/home/jenkins/.m2/wrapper"
      name: "volume-4"
      readOnly: false
    - mountPath: "/home/jenkins/.m2/settings.xml"
      name: "m2-secret-dir"
      readOnly: true
      subPath: "settings.xml"
    - mountPath: "/home/jenkins/.ssh"
      name: "volume-1"
      readOnly: false
    - mountPath: "/home/jenkins/agent"
      name: "workspace-volume"
      readOnly: false
    workingDir: "/home/jenkins/agent"
  nodeSelector:
    beta.kubernetes.io/os: "linux"
  restartPolicy: "Never"
  securityContext: {}
  volumes:
  - name: "volume-0"
    persistentVolumeClaim:
      claimName: "tools-claim-jiro-metro"
      readOnly: true
  - name: "m2-secret-dir"
    secret:
      secretName: "m2-secret-dir"
  - emptyDir:
      medium: ""
    name: "volume-2"
  - configMap:
      name: "m2-dir"
    name: "m2-dir"
  - configMap:
      name: "known-hosts"
    name: "volume-1"
  - emptyDir:
      medium: ""
    name: "workspace-volume"
  - emptyDir:
      medium: ""
    name: "volume-4"
  - emptyDir:
      medium: ""
    name: "volume-3"

Building remotely on basic-x8ct8 in workspace <https://ci.eclipse.org/metro/job/ws-test-harness-master-build/ws/>
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent]   Exec ssh-agent (binary ssh-agent on a remote machine)
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-S3Q1A05rEy2q/agent.66
SSH_AGENT_PID=68
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: <https://ci.eclipse.org/metro/job/ws-test-harness-master-build/ws/@tmp/private_key_15776384442752435162.key> (<https://ci.eclipse.org/metro/job/ws-test-harness-master-build/ws/@tmp/private_key_15776384442752435162.key)>
[ssh-agent] Using credentials eclipse-metro-bot (GitHub bot SSH)
The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/eclipse-ee4j/metro-ws-test-harness.git
 > git init <https://ci.eclipse.org/metro/job/ws-test-harness-master-build/ws/> # timeout=10
Fetching upstream changes from https://github.com/eclipse-ee4j/metro-ws-test-harness.git
 > git --version # timeout=10
 > git --version # 'git version 2.26.2'
 > git fetch --tags --force --progress -- https://github.com/eclipse-ee4j/metro-ws-test-harness.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/eclipse-ee4j/metro-ws-test-harness.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 11977d77ad97825a71e6fc2d223db71915d3bb6e (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 11977d77ad97825a71e6fc2d223db71915d3bb6e # timeout=10
Commit message: "Bump ant from 1.10.7 to 1.10.9"
 > git rev-list --no-walk af275cfa62ec8a0661ba3f81397a4082ae530bb7 # timeout=10
[ws-test-harness-master-build] $ /bin/sh -e /tmp/jenkins5986980890286040925.sh
-[ GPG Initialization ]---------------------------------------------------------
gpg: directory '/home/jenkins/.gnupg' created
gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created
gpg: key A7C6AFD280CA7CF0: 1 signature not checked due to a missing key
gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created
gpg: key A7C6AFD280CA7CF0: public key "Eclipse Metro <metro-dev@xxxxxxxxxxx>" imported
gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status
gpg: key A7C6AFD280CA7CF0: secret key imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg:       secret keys read: 1
gpg:   secret keys imported: 1
gpg: no ultimately trusted keys found
Secret subkeys are available.

pub  rsa4096/A7C6AFD280CA7CF0
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: unknown       validity: unknown
ssb  rsa4096/B6D3FC494798E478
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ unknown] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>

pub  rsa4096/A7C6AFD280CA7CF0
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: unknown       validity: unknown
ssb  rsa4096/B6D3FC494798E478
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ unknown] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>

Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)

  1 = I don't know or won't say
  2 = I do NOT trust
  3 = I trust marginally
  4 = I trust fully
  5 = I trust ultimately
  m = back to the main menu


pub  rsa4096/A7C6AFD280CA7CF0
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: unknown
ssb  rsa4096/B6D3FC494798E478
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ unknown] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>
Please note that the shown key validity is not necessarily correct
unless you restart the program.

Secret subkeys are available.

gpg: checking the trustdb
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: next trustdb check due at 2023-10-02
pub  rsa4096/A7C6AFD280CA7CF0
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: ultimate
ssb  rsa4096/B6D3FC494798E478
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ultimate] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>

pub  rsa4096/A7C6AFD280CA7CF0
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: ultimate
ssb  rsa4096/B6D3FC494798E478
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ultimate] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>

Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)

  1 = I don't know or won't say
  2 = I do NOT trust
  3 = I trust marginally
  4 = I trust fully
  5 = I trust ultimately
  m = back to the main menu


pub  rsa4096/A7C6AFD280CA7CF0
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: ultimate
ssb  rsa4096/B6D3FC494798E478
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ultimate] (1). Eclipse Metro <metro-dev@xxxxxxxxxxx>

-[ Harness Build ]--------------------------------------------------------------
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 6 modules...
[INFO] Installing Nexus Staging features:
[INFO]   ... total of 6 executions of maven-deploy-plugin replaced with nexus-staging-maven-plugin
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
[INFO] WS Test Framework                                                  [pom]
[INFO] WS Test Harness                                                    [pom]
[INFO] WS Test Harness Bootstrap                                          [jar]
[INFO] WS Test Harness Library                                            [jar]
[INFO] WS Test Harness Documentation                                      [pom]
[INFO] WS Test Harness Maven Plugin                              [maven-plugin]
[INFO] 
[INFO] ---------------< org.glassfish.metro:ws-test-framework >----------------
[INFO] Building WS Test Framework 3.0.0-SNAPSHOT                          [1/6]
[INFO] --------------------------------[ pom ]---------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ ws-test-framework ---
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-maven) @ ws-test-framework ---
[INFO] 
[INFO] --- glassfish-copyright-maven-plugin:2.3:check (copyright-check) @ ws-test-framework ---
[ERROR] Errors: 1
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for WS Test Framework 3.0.0-SNAPSHOT:
[INFO] 
[INFO] WS Test Framework .................................. FAILURE [ 19.152 s]
[INFO] WS Test Harness .................................... SKIPPED
[INFO] WS Test Harness Bootstrap .......................... SKIPPED
[INFO] WS Test Harness Library ............................ SKIPPED
[INFO] WS Test Harness Documentation ...................... SKIPPED
[INFO] WS Test Harness Maven Plugin ....................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  37.851 s
[INFO] Finished at: 2021-02-07T15:28:17Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.glassfish.copyright:glassfish-copyright-maven-plugin:2.3:check (copyright-check) on project ws-test-framework: Copyright checking failed -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 68 killed;
[ssh-agent] Stopped.
Recording test results
[Checks API] No suitable checks publisher found.


Back to the top