Started by timer Running as SYSTEM Agent centos-8-ppt5b is provisioned from template centos-8 --- apiVersion: "v1" kind: "Pod" metadata: labels: jenkins: "slave" jenkins/label-digest: "dcdbc7ed8a3e8b49b8443ee4b54d9618b35139e6" jenkins/label: "centos-latest_centos-8" name: "centos-8-ppt5b" namespace: "releng" spec: containers: - env: - name: "JENKINS_SECRET" value: "********" - name: "JENKINS_TUNNEL" value: "jenkins-discovery.releng.svc.cluster.local:50000" - name: "JENKINS_AGENT_NAME" value: "centos-8-ppt5b" - 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: "centos-8-ppt5b" - name: "JENKINS_AGENT_WORKDIR" value: "/home/jenkins/agent" - name: "JENKINS_URL" value: "http://jenkins-ui.releng.svc.cluster.local/releng/" image: "docker.io/eclipsecbi/jiro-agent-centos-8:remoting-3160.vd76b_9ddd10cc" imagePullPolicy: "Always" name: "jnlp" resources: limits: cpu: "2000m" memory: "4096Mi" requests: cpu: "1000m" memory: "4096Mi" tty: true volumeMounts: - mountPath: "/home/jenkins/.m2/settings-deploy-ossrh-releng.xml" name: "m2-secret-dir" readOnly: true subPath: "settings-deploy-ossrh-releng.xml" - 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-deploy-ossrh-pde.xml" name: "m2-secret-dir" readOnly: true subPath: "settings-deploy-ossrh-pde.xml" - 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/.m2/settings-deploy-ossrh-jdt.xml" name: "m2-secret-dir" readOnly: true subPath: "settings-deploy-ossrh-jdt.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-releng" 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 centos-8-ppt5b (centos-8 centos-latest) in workspace /home/jenkins/agent/workspace/rt.equinox.releng.cleanupDLsite [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-hxs1elOVp3H9/agent.44 SSH_AGENT_PID=46 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /home/jenkins/agent/workspace/rt.equinox.releng.cleanupDLsite@tmp/private_key_7902546273938609828.key (/home/jenkins/agent/workspace/rt.equinox.releng.cleanupDLsite@tmp/private_key_7902546273938609828.key) [ssh-agent] Using credentials genie.releng (ssh://genie.releng@projects-storage.eclipse.org) [GitCheckoutListener] SCM 'hudson.scm.NullSCM' is not of type GitSCM No emails were triggered. [rt.equinox.releng.cleanupDLsite] $ /bin/sh -xe /tmp/jenkins11858975442701232010.sh + wget --no-proxy https://raw.githubusercontent.com/eclipse-platform/eclipse.platform.releng.aggregator/master/cje-production/cleaners/cleanupEquinox.sh --2024-04-18 11:45:09-- https://raw.githubusercontent.com/eclipse-platform/eclipse.platform.releng.aggregator/master/cje-production/cleaners/cleanupEquinox.sh Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.111.133, 185.199.108.133, 185.199.109.133, ... Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.111.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 1105 (1.1K) [text/plain] Saving to: ‘cleanupEquinox.sh’ 0K . 100% 85.7M=0s 2024-04-18 11:45:09 (85.7 MB/s) - ‘cleanupEquinox.sh’ saved [1105/1105] + ssh genie.releng@projects-storage.eclipse.org Pseudo-terminal will not be allocated because stdin is not a terminal. Welcome to Ubuntu 22.04.3 LTS (GNU/Linux 5.15.0-101-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: https://ubuntu.com/advantage System information as of Thu Apr 18 07:44:19 EDT 2024 System load: 0.005859375 Users logged in: 0 Usage of /: 9.2% of 57.97GB IPv4 address for ens2: 172.30.206.150 Memory usage: 15% IPv4 address for ens2: 198.41.30.204 Swap usage: 0% IPv4 address for ens2: 172.16.102.3 Processes: 130 IPv4 address for ens3: 172.25.25.150 * Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s just raised the bar for easy, resilient and secure K8s cluster deployment. https://ubuntu.com/engage/secure-kubernetes-at-the-edge Expanded Security Maintenance for Applications is not enabled. 49 updates can be applied immediately. To see these additional updates run: apt list --upgradable 2 additional security updates can be applied with ESM Apps. Learn more about enabling ESM Apps service at https://ubuntu.com/esm New release '23.10' available. Run 'do-release-upgrade' to upgrade to it. *** System restart required *** Current date: 2024 0418 07:45 Removing drops from downloads server at /home/data/httpd/download.eclipse.org/equinox/drops Deleting: I20240415-1800 $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 46 killed; [ssh-agent] Stopped. No emails were triggered. Finished: SUCCESS