Started by an SCM change Running as SYSTEM Building in workspace /var/jenkins/workspace/emf-validation-all [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-XXXXXXLhi3hW/agent.311417 SSH_AGENT_PID=311421 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /var/jenkins/workspace/emf-validation-all@tmp/private_key_14044497100577947072.key (/var/jenkins/workspace/emf-validation-all@tmp/private_key_14044497100577947072.key) [ssh-agent] Using credentials genie.emfservices (ssh://genie.emfservices@projects-storage.eclipse.org) The recommended git tool is: NONE No credentials specified > git rev-parse --resolve-git-dir /var/jenkins/workspace/emf-validation-all/.git # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/eclipse-emfservices/emf-validation.git # timeout=10 Fetching upstream changes from https://github.com/eclipse-emfservices/emf-validation.git > git --version # timeout=10 > git --version # 'git version 2.43.0' > git fetch --tags --force --progress -- https://github.com/eclipse-emfservices/emf-validation.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 1e3d98661b476ab2fee6c18d598f2324eb84aab5 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 1e3d98661b476ab2fee6c18d598f2324eb84aab5 # timeout=10 Commit message: "[releng] Add 2024-03 target platform" > git rev-list --no-walk 052bad3542428a9bd3da9903a2be131effd005d9 # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Triggering emf-validation-all » 2022-12,temurin-jdk17-latest,migration Triggering emf-validation-all » canary,temurin-jdk17-latest,migration Triggering emf-validation-all » 2023-06,temurin-jdk17-latest,migration Triggering emf-validation-all » 2023-03,temurin-jdk17-latest,migration Triggering emf-validation-all » 2023-09,temurin-jdk17-latest,migration Triggering emf-validation-all » 2023-12,temurin-jdk17-latest,migration Triggering emf-validation-all » 2022-09,temurin-jdk17-latest,migration Configuration emf-validation-all » 2022-12,temurin-jdk17-latest,migration is still in the queue: Waiting for next available executor on ‘migration’ emf-validation-all » 2022-12,temurin-jdk17-latest,migration completed with result SUCCESS Configuration emf-validation-all » canary,temurin-jdk17-latest,migration is still in the queue: Waiting for next available executor on ‘migration’ emf-validation-all » canary,temurin-jdk17-latest,migration completed with result SUCCESS emf-validation-all » 2023-06,temurin-jdk17-latest,migration completed with result SUCCESS Configuration emf-validation-all » 2023-03,temurin-jdk17-latest,migration is still in the queue: All nodes of label ‘migration’ are offline Configuration emf-validation-all » 2023-03,temurin-jdk17-latest,migration is still in the queue: Waiting for next available executor on ‘migration’ emf-validation-all » 2023-03,temurin-jdk17-latest,migration completed with result SUCCESS emf-validation-all » 2023-09,temurin-jdk17-latest,migration completed with result SUCCESS Configuration emf-validation-all » 2023-12,temurin-jdk17-latest,migration is still in the queue: Waiting for next available executor Configuration emf-validation-all » 2023-12,temurin-jdk17-latest,migration is still in the queue: All nodes of label ‘migration’ are offline Configuration emf-validation-all » 2023-12,temurin-jdk17-latest,migration is still in the queue: Waiting for next available executor on ‘migration’ emf-validation-all » 2023-12,temurin-jdk17-latest,migration completed with result SUCCESS emf-validation-all » 2022-09,temurin-jdk17-latest,migration completed with result SUCCESS $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 311421 killed; [ssh-agent] Stopped. Finished: SUCCESS