Build fail because of build script error

Fabian Deutsch fdeutsch at redhat.com
Fri Jan 8 07:26:13 UTC 2016


On Fri, Jan 8, 2016 at 12:19 AM, Nir Soffer <nsoffer at redhat.com> wrote:
> Hi all,
>
> All the vdsm builds seem to fail now because of this error:
>
> 23:11:19 + loops=($(losetup -a     | grep -E "$WORKSPACE|\(build/disk"
>     | awk '{print $1}'     | sed -e 's/://'))
> 23:11:19 ++ losetup -a
> 23:11:19 /tmp/hudson7768123740643865272.sh: line 80: losetup: command not found
> 23:11:19 ++ grep -E
> '/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64|\(build/disk'
> 23:11:19 ++ awk '{print $1}'
> 23:11:19 ++ sed -e s/://
> 23:11:19 + [[ -n '' ]]
> 23:11:19 /tmp/hudson7768123740643865272.sh: line 87: syntax error near
> unexpected token `\ '
> 23:11:19 POST BUILD TASK : FAILURE
> 23:11:19 END OF POST BUILD TASK : 0
> 23:11:19 ESCALATE FAILED POST BUILD TASK TO JOB STATUS
> 23:11:19 Build step 'Post build task' changed build result to FAILURE
> 23:11:19 Archiving artifacts
> 23:11:22 Build step 'Groovy Postbuild' marked build as failure
> 23:11:22 Finished: FAILURE
>
> See http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/1978/console
>
> Can someone from infra can look into this error?

+1

- fabian



More information about the Infra mailing list