maas-builds team mailing list archive
-
maas-builds team
-
Mailing list archive
-
Message #02482
debug-ws-error - Build # 11 - Still Failing! - Built with lp:maas (revno: -1) and lp:~maas-maintainers/maas/packaging (revno: -1)
Built with lp:maas (revno: -1) and lp:~maas-maintainers/maas/packaging (revno: -1)
See http://162.213.35.104:8080/job/debug-ws-error/11/
Started by user admin
Building remotely on lenovo-RD230-01 in workspace /var/lib/jenkins/workspace/debug-ws-error
No emails were triggered.
[debug-ws-error] $ /bin/bash -ex /tmp/hudson5283575582531775775.sh
+ rm -Rf maas maas-ci-config packaging results
+ export http_proxy=http://162.213.35.104:3128
+ http_proxy=http://162.213.35.104:3128
+ export https_proxy=http://162.213.35.104:3128
+ https_proxy=http://162.213.35.104:3128
+ bzr checkout --revision -1 --lightweight lp:maas maas
++ bzr revno --tree maas
+ export MAAS_BRANCH_REVNO=5215
+ MAAS_BRANCH_REVNO=5215
+ bzr checkout --revision -1 --lightweight 'lp:~maas-maintainers/maas/packaging' packaging
++ bzr revno --tree packaging
+ export PACKAGING_REVNO=509
+ PACKAGING_REVNO=509
+ bzr checkout -r440 --lightweight '~brendan-donegan/maas/juju_bootstrap_debug' qa-lab-tests
bzr: ERROR: Not a branch: "/var/lib/jenkins/workspace/debug-ws-error/~brendan-donegan/maas/juju_bootstrap_debug/".
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Follow ups
References