Bug 10786 - Missing adt repo for 2.0.3 build
Summary: Missing adt repo for 2.0.3 build
Status: RESOLVED FIXED
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: 2.0.3
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.0.3
Assignee: Joshua Lock
QA Contact: Yi Zhao
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-12-12 05:17 UTC by Yi Zhao
Modified: 2017-01-12 16:21 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Found by QA test)
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2016-12-12 05:17:46 UTC
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!!!
#######################
Comment 1 Joshua Lock 2016-12-12 12:11:09 UTC
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…
Comment 2 Joshua Lock 2016-12-12 15:35:52 UTC
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.
Comment 3 Michael Halstead 2016-12-12 17:59:40 UTC
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.