![[Jenkins]](/yasson/static/8d4c90af/images/svgs/logo.svg){kind=logo}
Started by an SCM change Running as SYSTEM Agent basic-mjlrs is provisioned from template basic --- apiVersion: "v1" kind: "Pod" metadata: annotations: {} labels: jenkins: "slave" jenkins/label-digest: "61a7508ed1b04e9ada836fcd14d4d8ef5687c7dd" jenkins/label: "basic" name: "basic-mjlrs" spec: containers: - env: - name: "JENKINS_SECRET" value: "********" - name: "JENKINS_TUNNEL" value: "jenkins-discovery.yasson.svc.cluster.local:50000" - name: "JENKINS_AGENT_NAME" value: "basic-mjlrs" - name: "JENKINS_REMOTING_JAVA_OPTS" value: "-showversion -XshowSettings:vm -Xmx256m -Dorg.jenkinsci.remoting.engine.JnlpProtocol3.disabled=true\ \ -Dorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.useSETSID=true" - name: "JAVA_TOOL_OPTIONS" value: "" - name: "_JAVA_OPTIONS" value: "" - name: "OPENJ9_JAVA_OPTIONS" value: "-XX:+IgnoreUnrecognizedVMOptions -XX:+IdleTuningCompactOnIdle -XX:+IdleTuningGcOnIdle" - name: "JENKINS_NAME" value: "basic-mjlrs" - name: "JENKINS_AGENT_WORKDIR" value: "/home/jenkins/agent" - name: "JENKINS_URL" value: "http://jenkins-ui.yasson.svc.cluster.local/yasson/" image: "docker.io/eclipsecbi/jiro-agent-basic:remoting-4.11.2" imagePullPolicy: "Always" name: "jnlp" resources: limits: cpu: "2000m" memory: "4096Mi" requests: cpu: "1000m" memory: "4096Mi" 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 subPath: "" - mountPath: "/home/jenkins/agent" name: "workspace-volume" readOnly: false workingDir: "/home/jenkins/agent" nodeSelector: kubernetes.io/os: "linux" restartPolicy: "Never" volumes: - name: "volume-0" persistentVolumeClaim: claimName: "tools-claim-jiro-yasson" 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-mjlrs (basic) in workspace /home/jenkins/agent/workspace/yasson-build [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-X4pDadH8fF8X/agent.62 SSH_AGENT_PID=64 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /home/jenkins/agent/workspace/yasson-build@tmp/private_key_10009432887042844407.key (/home/jenkins/agent/workspace/yasson-build@tmp/private_key_10009432887042844407.key) [ssh-agent] Using credentials yasson-bot (GitHub bot SSH) The recommended git tool is: NONE No credentials specified Cloning the remote Git repository Cloning repository https://github.com/eclipse/yasson.git > git init /home/jenkins/agent/workspace/yasson-build # timeout=10 Fetching upstream changes from https://github.com/eclipse/yasson.git > git --version # timeout=10 > git --version # 'git version 2.20.1' > git fetch --tags --force --progress -- https://github.com/eclipse/yasson.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/eclipse/yasson.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 Avoid second fetch > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 423ed93aa13d04a664c2c32010df2fce96f90079 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 423ed93aa13d04a664c2c32010df2fce96f90079 # timeout=10 Commit message: "JSONB tck re-enabled (#538)" > git rev-list --no-walk b74033d37ea6f1cb297922540131eb4a483dc24e # timeout=10 [yasson-build] $ /bin/sh -xe /tmp/jenkins7010535141019417477.sh + gpg --batch --import **** gpg: directory '/home/jenkins/.gnupg' created gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created gpg: key B11A29C468F7EA64: public key "Eclipse Yasson Project <yasson-dev@eclipse.org>" imported gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status gpg: key B11A29C468F7EA64: secret key imported gpg: Total number processed: 1 gpg: imported: 1 gpg: secret keys read: 1 gpg: secret keys imported: 1 ++ gpg --list-keys --with-colons ++ awk -F: '/fpr:/ {print $10}' ++ sort -u + for fpr in $(gpg --list-keys --with-colons | awk -F: '/fpr:/ {print $10}' | sort -u) + echo -e '5\ny\n' + gpg --batch --command-fd 0 --expert --edit-key 5FCBD56B27BC981F218DBC24FDE958769183CDB3 trust Secret subkeys are available. pub rsa4096/B11A29C468F7EA64 created: 2017-05-30 expires: 2022-05-29 usage: SCEA trust: unknown validity: unknown ssb rsa4096/FDE958769183CDB3 created: 2017-05-30 expires: 2022-05-29 usage: S [ unknown] (1). Eclipse Yasson Project <yasson-dev@eclipse.org> pub rsa4096/B11A29C468F7EA64 created: 2017-05-30 expires: 2022-05-29 usage: SCEA trust: unknown validity: unknown ssb rsa4096/FDE958769183CDB3 created: 2017-05-30 expires: 2022-05-29 usage: S [ unknown] (1). Eclipse Yasson Project <yasson-dev@eclipse.org> 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/B11A29C468F7EA64 created: 2017-05-30 expires: 2022-05-29 usage: SCEA trust: ultimate validity: unknown ssb rsa4096/FDE958769183CDB3 created: 2017-05-30 expires: 2022-05-29 usage: S [ unknown] (1). Eclipse Yasson Project <yasson-dev@eclipse.org> Please note that the shown key validity is not necessarily correct unless you restart the program. + for fpr in $(gpg --list-keys --with-colons | awk -F: '/fpr:/ {print $10}' | sort -u) + echo -e '5\ny\n' + gpg --batch --command-fd 0 --expert --edit-key AB70E95978F7F235EE94C920B11A29C468F7EA64 trust 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 2022-05-29 pub rsa4096/B11A29C468F7EA64 created: 2017-05-30 expires: 2022-05-29 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/FDE958769183CDB3 created: 2017-05-30 expires: 2022-05-29 usage: S [ultimate] (1). Eclipse Yasson Project <yasson-dev@eclipse.org> pub rsa4096/B11A29C468F7EA64 created: 2017-05-30 expires: 2022-05-29 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/FDE958769183CDB3 created: 2017-05-30 expires: 2022-05-29 usage: S [ultimate] (1). Eclipse Yasson Project <yasson-dev@eclipse.org> 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/B11A29C468F7EA64 created: 2017-05-30 expires: 2022-05-29 usage: SCEA trust: ultimate validity: ultimate ssb rsa4096/FDE958769183CDB3 created: 2017-05-30 expires: 2022-05-29 usage: S [ultimate] (1). Eclipse Yasson Project <yasson-dev@eclipse.org> [yasson-build] $ /opt/tools/apache-maven/latest/bin/mvn -f pom.xml -Dmaven.repo.local=/home/jenkins/agent/workspace/yasson-build/.repository dependency:purge-local-repository -B [INFO] Scanning for projects... [INFO] [INFO] -------------------------< org.eclipse:yasson >------------------------- [INFO] Building Yasson 3.0.0-SNAPSHOT [INFO] --------------------------------[ jar ]--------------------------------- [INFO] [INFO] --- maven-dependency-plugin:2.8:purge-local-repository (default-cli) @ yasson --- [WARNING] The artifact xml-apis:xml-apis:jar:2.0.2 has been relocated to xml-apis:xml-apis:jar:1.0.b2 [WARNING] Missing POM for jakarta.json.bind:jakarta.json.bind-api:jar:3.0.0-RC1 [WARNING] Missing POM for jakarta.json:jakarta.json-api:jar:2.1.0 [WARNING] Missing POM for org.eclipse.parsson:parsson:jar:1.1.0 [WARNING] Missing POM for jakarta.el:jakarta.el-api:jar:5.0.0 [INFO] Unable to resolve all dependencies for : org.eclipse:yasson:3.0.0-SNAPSHOT. Falling back to non-transitive mode for initial artifact resolution. [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 11.741 s [INFO] Finished at: 2022-02-16T19:15:45Z [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:purge-local-repository (default-cli) on project yasson: Failed to refresh project dependencies for: org.eclipse:yasson:jar:3.0.0-SNAPSHOT: required artifacts missing: [ERROR] jakarta.json.bind:jakarta.json.bind-api:jar:3.0.0-RC1 [ERROR] jakarta.json:jakarta.json-api:jar:2.1.0 [ERROR] org.eclipse.parsson:parsson:jar:1.1.0 [ERROR] [ERROR] for the artifact: [ERROR] org.eclipse:yasson:jar:3.0.0-SNAPSHOT [ERROR] [ERROR] from the specified remote repositories: [ERROR] eclipse.maven.central.mirror (https://repo.eclipse.org/content/repositories/maven_central/, releases=true, snapshots=false) [ERROR] -> [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/MojoFailureException Build step 'Invoke top-level Maven targets' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 64 killed; [ssh-agent] Stopped. Recording test results ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? [Java CompilerJavaDocSpotBugs] Skipping execution of recorder since overall result is 'FAILURE' Finished: FAILURE