aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1138) aurorabuild.sh should exit on error in any command
Date Sun, 22 Feb 2015 18:21:11 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332278#comment-14332278
] 

Bill Farner commented on AURORA-1138:
-------------------------------------

Thanks for filing!  I've been burned by this too, but was delinquent in fixing or tracking
with a ticket.  I can likely address this in the coming week, unless you beat me to it :-)

> aurorabuild.sh should exit on error in any command
> --------------------------------------------------
>
>                 Key: AURORA-1138
>                 URL: https://issues.apache.org/jira/browse/AURORA-1138
>             Project: Aurora
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 0.7.0
>         Environment: Vagrant from examples/vagrant
>            Reporter: Thorhallur Sverrisson
>            Priority: Trivial
>              Labels: easyfix
>
> Due to proxy issues the mesos native egg could not be downloaded, but the scripts continued
to completion.  This resulted in termos_observer.pex being a plain .zip file which failed
to execute.
> Not many hits on google regarding that issue, but I managed to find a link to an issue
where the native egg had been moved from mesosphere to svn.apache.org which led me to rerun
the 'aurorabuild.sh executor' and watching the output more closely.  Lo and behold there was
an error in the compilation.
> Having a 'set -e' at the top of the provision and aurorabuild scripts would have indicated
the problem right away.  It could also flush out other issues that may be present.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message