Started by timer
Building remotely on s390x (metal-s390x) in workspace /var/lib/jenkins/slaves/s390x/workspace/virt-in-release-s390x-x
[virt-in-release-s390x-x] $ /bin/bash -eu /tmp/jenkins602423192120216435.sh
Cloning into 'qemu-migration-test'...
fatal: unable to access 'https://git.launchpad.net/~ubuntu-server/ubuntu/+source/qemu-migration-test/': The requested URL returned error: 503
Build step 'Execute shell' marked build as failure
Sending e-mails to: email@example.com
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: Test reports were found but none of them are new. Did tests run?
For example, /var/lib/jenkins/slaves/s390x/workspace/virt-in-release-s390x-x/result.xml is 3 days 22 hr old
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Triggering a new build of virt-in-release-s390x-z