FailedConsole Output

Started by timer
Running as SYSTEM
Agent default-agent-j29jw is provisioned from template Kubernetes Pod Template
---
apiVersion: "v1"
kind: "Pod"
metadata:
  annotations: {}
  labels:
    jenkins: "slave"
  name: "default-agent-j29jw"
spec:
  containers:
  - env:
    - name: "MAVEN_OPTS"
      value: "-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn"
    - name: "JENKINS_SECRET"
      value: "********"
    - name: "JENKINS_TUNNEL"
      value: "jenkins-discovery.openk-usermodules.svc.cluster.local:50000"
    - name: "JENKINS_AGENT_NAME"
      value: "default-agent-j29jw"
    - name: "MAVEN_CONFIG"
      value: "-B -e"
    - name: "JENKINS_NAME"
      value: "default-agent-j29jw"
    - name: "JENKINS_AGENT_WORKDIR"
      value: "/home/jenkins/agent"
    - name: "JENKINS_URL"
      value: "http://jenkins-ui.openk-usermodules.svc.cluster.local/openk-usermodules/"
    - name: "HOME"
      value: "/home/jenkins"
    image: "eclipsecbijenkins/jenkins-agent:3.29@sha256:d7df679b5f7337f1bf77922400a148b80e3c483ccba72933a18f0c87be98f8b1"
    imagePullPolicy: "IfNotPresent"
    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: "toolchains-xml"
      readOnly: true
      subPath: "toolchains.xml"
    - 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: "settings-security-xml"
      readOnly: true
      subPath: "settings-security.xml"
    - mountPath: "/home/jenkins/.m2/settings.xml"
      name: "settings-xml"
      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: {}
  restartPolicy: "Never"
  volumes:
  - name: "settings-security-xml"
    secret:
      items:
      - key: "settings-security.xml"
        path: "settings-security.xml"
      secretName: "m2-secret-dir"
  - name: "volume-0"
    persistentVolumeClaim:
      claimName: "tools-claim-jiro-openk-usermodules"
      readOnly: true
  - configMap:
      items:
      - key: "toolchains.xml"
        path: "toolchains.xml"
      name: "m2-dir"
    name: "toolchains-xml"
  - emptyDir:
      medium: ""
    name: "volume-2"
  - configMap:
      name: "known-hosts"
    name: "volume-1"
  - name: "settings-xml"
    secret:
      items:
      - key: "settings.xml"
        path: "settings.xml"
      secretName: "m2-secret-dir"
  - emptyDir:
      medium: ""
    name: "workspace-volume"
  - emptyDir:
      medium: ""
    name: "volume-3"

Building remotely on default-agent-j29jw in workspace /home/jenkins/agent/workspace/ok-standby-planning-frontend
No credentials specified
Cloning the remote Git repository
Cloning repository https://git.eclipse.org/r/openk-usermodules/org.eclipse.openk-usermodules.standbyPlanning.frontend
 > git init /home/jenkins/agent/workspace/ok-standby-planning-frontend # timeout=10
Fetching upstream changes from https://git.eclipse.org/r/openk-usermodules/org.eclipse.openk-usermodules.standbyPlanning.frontend
 > git --version # timeout=10
 > git fetch --tags --force --progress https://git.eclipse.org/r/openk-usermodules/org.eclipse.openk-usermodules.standbyPlanning.frontend +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://git.eclipse.org/r/openk-usermodules/org.eclipse.openk-usermodules.standbyPlanning.frontend # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://git.eclipse.org/r/openk-usermodules/org.eclipse.openk-usermodules.standbyPlanning.frontend # timeout=10
Fetching upstream changes from https://git.eclipse.org/r/openk-usermodules/org.eclipse.openk-usermodules.standbyPlanning.frontend
 > git fetch --tags --force --progress https://git.eclipse.org/r/openk-usermodules/org.eclipse.openk-usermodules.standbyPlanning.frontend +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 6953c38027dd236fdd131beebe19c0be68589151 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 6953c38027dd236fdd131beebe19c0be68589151 # timeout=10
Commit message: "BP 839: add meta tag to enforce internet explorer 11"
 > git rev-list --no-walk 6953c38027dd236fdd131beebe19c0be68589151 # timeout=10
Unpacking https://nodejs.org/dist/v10.8.0/node-v10.8.0-linux-x64.tar.gz to /home/jenkins/agent/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-10.8.0 on default-agent-j29jw
[ok-standby-planning-frontend] $ /bin/sh -xe /tmp/jenkins1506000027619068061.sh
+ rm -rf node_modules
+ npm i

> uws@9.14.0 install /home/jenkins/agent/workspace/ok-standby-planning-frontend/node_modules/uws
> node-gyp rebuild > build_log.txt 2>&1 || exit 0


> node-sass@4.9.0 install /home/jenkins/agent/workspace/ok-standby-planning-frontend/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.9.0/linux-x64-64_binding.node
Download complete
Binary saved to /home/jenkins/agent/workspace/ok-standby-planning-frontend/node_modules/node-sass/vendor/linux-x64-64/binding.node
Caching binary to /home/jenkins/.npm/node-sass/4.9.0/linux-x64-64_binding.node

> node-sass@4.9.0 postinstall /home/jenkins/agent/workspace/ok-standby-planning-frontend/node_modules/node-sass
> node scripts/build.js

Binary found at /home/jenkins/agent/workspace/ok-standby-planning-frontend/node_modules/node-sass/vendor/linux-x64-64/binding.node
Testing binary
Binary is fine
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1194 packages from 1394 contributors and audited 23320 packages in 58.372s
found 410 vulnerabilities (4 low, 36 moderate, 368 high, 2 critical)
  run `npm audit fix` to fix them, or `npm audit` for details
+ npm run test

> bereitschaftsplanung@0.8.0 test /home/jenkins/agent/workspace/ok-standby-planning-frontend
> ng test --browsers=ChromeHeadless --watch=false --code-coverage

  0% compiling 10% building modules 0/1 modules 1 active …ndby-planning-frontend/src/polyfills.ts                                          10% building modules 1/1 modules 0 active(node:246) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
 10% building modules 1/2 modules 1 active …k-standby-planning-frontend/src/test.ts 10% building modules 1/3 modules 2 active …ndby-planning-frontend/src/polyfills.ts 10% building modules 2/3 modules 1 active …ndby-planning-frontend/src/polyfills.ts                                          10% building modules 3/3 modules 0 active 10% building modules 3/4 modules 1 active …lanning-frontend/src sync /\.spec\.ts$/15 12 2019 06:35:17.509:INFO [karma]: Karma v2.0.4 server started at http://0.0.0.0:9876/
15 12 2019 06:35:17.513:INFO [launcher]: Launching browser ChromeHeadless with unlimited concurrency
15 12 2019 06:35:17.523:INFO [launcher]: Starting browser ChromeHeadless
15 12 2019 06:35:17.524:ERROR [launcher]: No binary for ChromeHeadless browser on your platform.
  Please, set "CHROME_BIN" env variable.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bereitschaftsplanung@0.8.0 test: `ng test --browsers=ChromeHeadless --watch=false --code-coverage`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the bereitschaftsplanung@0.8.0 test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/jenkins/.npm/_logs/2019-12-15T06_35_17_601Z-debug.log
Build step 'Execute shell' marked build as failure
Finished: FAILURE