[Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 128 - Failure!

[Scott Little]

Error message suggests we ran out of space on /tmp within the docker 
building stx-nova

mkdir -p /tmp/wheels/
tar xf /tmp/wheels.tar.gz '--exclude=.*' -C /tmp/wheels/
PuLP-1.6.9-py2-none-any.whl: Wrote only 512 of 10240 bytes
pycadf-2.9.0-py2.py3-none-any.whl: Cannot open: No space left on device
pycparser-2.19-py2.py3-none-any.whl: Cannot open: No space left on device

/dev on build host was down to a 64 M

Cleaning some old docker containers/images and restarting the build...


Scott


On 2019-10-03 10:29 p.m., build.starlingx at gmail.com wrote:
> Project: STX_build_docker_flock_images
> Build #: 128
> Status: Failure
> Timestamp: 20191003T234444Z
>
> Check logs at:
> http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs
> --------------------------------------------------------------------------------
> Parameters
>
> HOST_PORT: 80
> MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-2.0/20191003T205840Z
> OS: centos
> MY_REPO: /localdisk/designer/jenkins/rc-2.0/cgcs-root
> BASE_VERSION: rc-2.0-stable-20191003T205840Z
> PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs
> REGISTRY_USERID: slittlewrs
> HOST: build.starlingx.cengn.ca
> LATEST_PREFIX: rc-2.0
> PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs
> PUBLISH_TIMESTAMP: 20191003T205840Z
> FLOCK_VERSION: rc-2.0-centos-stable-20191003T205840Z
> PREFIX: rc-2.0
> TIMESTAMP: 20191003T205840Z
> BUILD_STREAM: stable
> REGISTRY_ORG: starlingx
> PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191003T205840Z/outputs
> REGISTRY: docker.io
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20191004/13c1aa64/attachment.html>