hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From schubert <...@git.apache.org>
Subject [GitHub] incubator-hawq pull request: HAWQ-597. Add Travis CI(OSX)
Date Mon, 28 Mar 2016 17:31:20 GMT
Github user schubert commented on the pull request:

    https://github.com/apache/incubator-hawq/pull/513#issuecomment-202498534
  
    I saw this warning in the build:
    
    `This log is too long to be displayed. Please reduce the verbosity of your build or download
the raw log.`
    
    Due to what looks like Travis's limitation of 10,000 lines displayed for the build log,
I would recommend you pipe non-essential information to a file and only print out in an error
condition so you minimize the log noise and usually only see essential build output without
having to look at the raw log.
    
    you can do this for example with brew update: 
    
    ```bash
    brew update 2>&1 > /tmp/brew-update.txt || (cat /tmp/brew-update.txt &&
false)
    ```
    
    Redirect stderr to stdout and if you get a non-zero exit, print out the logfile of what
happened and stop the build. 
    
    I think you would want to do this for everything in the `before_install` and in the `install`
with the exception of libhdfs3 due to it being a tightly coupled and relevant dependency.
Maybe move libhdfs3 down into the before_script to make that separation clear?
    
    Hopefully with that all of the critical build steps relevant to HAWQ itself will be displayed
the vast majority of the time to make it more developer friendly.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message