10786 2016-12-12 05:17:46 +0000 Missing adt repo for 2.0.3 build 2017-01-12 16:21:04 +0000 1 1 5 Infrastructure AutoBuilder autobuilder 2.0.3 x86 Multiple RESOLVED FIXED Medium+ normal 2.0.3 1 yi.zhao joshuagloe infras.ab.watcher Infras.watcher jose.perez.carranza mhalstead pidge yi.zhao --- Regression (Found by QA test) No (bug/feature does not impact docs) oldest_to_newest 69028 0 yi.zhao 2016-12-12 05:17:46 +0000 adt-installer: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.3.rc6/adt-installer-QA/ There is no adt repo for 2.0.3 rc6 build: ##################### --2016-12-12 09:52:40-- http://adtrepo-dev.yoctoproject.org//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro Resolving adtrepo-dev.yoctoproject.org (adtrepo-dev.yoctoproject.org)... 140.211.169.59 Connecting to adtrepo-dev.yoctoproject.org (adtrepo-dev.yoctoproject.org)|140.211.169.59|:80... connected. HTTP request sent, awaiting response... 404 Not Found Remote file does not exist -- broken link!!! ####################### 69033 1 joshuagloe 2016-12-12 12:11:09 +0000 Publishing of the adt-repo has indeed failed: https://autobuilder.yoctoproject.org/main/builders/nightly/builds/1108/steps/Publishing%20Artifacts_1/logs/stdio mkdir: cannot create directory ‘/srv/www/vhosts/adtrepo-dev’: Permission denied sending incremental file list rsync: mkdir "/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/adt-ipk" failed: No such file or directory (2) rsync error: error in file IO (code 11) at main.c(674) [Receiver=3.1.1] mkdir: cannot create directory ‘/srv/www/vhosts/adtrepo-dev’: Permission denied ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemuarm’: No such file or directory ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemuarm64’: No such file or directory ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemuarm-lsb’: No such file or directory ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemumips’: No such file or directory ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemumips64’: No such file or directory ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemumips-lsb’: No such file or directory ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemuppc’: No such file or directory ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemuppc-lsb’: No such file or directory ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemux86’: No such file or directory ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemux86-64’: No such file or directory ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemux86-64-lsb’: No such file or directory ln: failed to create symbolic link ‘/srv/www/vhosts/adtrepo-dev//2.0.3-adb34b8ddcd8cc34ae7d2b1b2e4b4d291d790f56-jethro/rootfs/qemux86-lsb’: No such file or directory This should have resulted in a build failure too… 69041 2 joshuagloe 2016-12-12 15:35:52 +0000 I need to work with Michael on understanding why the autobuilder is configured to publish the ADT repo to a non-existent directory. In the meantime I've written a patch to ensure such a failure causes the PublishArtifacts step to fail. 69044 3 mhalstead 2016-12-12 17:59:40 +0000 I've re-added /srv/www/vhosts/adtrepo-dev for builds that need it. When ADT was retired we removed this directory. I'm not sure if it was on purpose or on accident. This should fix the problem until we are really done with ADT.