[jira] [Commented] (CALCITE-1412) Use Wercker instead of Travis-CI
[ https://issues.apache.org/jira/browse/CALCITE-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15547140#comment-15547140 ] Francis Chuang commented on CALCITE-1412: - [~julianhyde] Wercker has a build status image, just like the one used in travis. For example, here's the one for my fork's use-wercker branch: https://app.wercker.com/status/23565d2b5a556e4c73c18696654a432f/s/use-wercker After enabling the textExaplinJoin3 test, the build failed on both JDK-7 and JDK-8, this does not seem to be a timeout, but rather the test not passing. See here for the logs: https://app.wercker.com/F21/calcite/runs/build-jdk-7/57f4431f072c590100317557?step=57f44325ec04d50001ba11cf > Use Wercker instead of Travis-CI > > > Key: CALCITE-1412 > URL: https://issues.apache.org/jira/browse/CALCITE-1412 > Project: Calcite > Issue Type: Bug >Reporter: Julian Hyde >Assignee: Francis Chuang > > There are reports that Wercker is less prone to hanging when running tests > than Travis CI. We should investigate. > [~francischuang], can you attach a pull request? > Does Wercker have an equivalent of the "build status" at the top of README.md? > Also can you see whether you can re-enable JdbcTest.testExplainJoin3 (which > is disabled due to OutOfMemoryError on Travis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CALCITE-1412) Use Wercker instead of Travis-CI
[ https://issues.apache.org/jira/browse/CALCITE-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15547155#comment-15547155 ] Francis Chuang commented on CALCITE-1412: - [~elserj] also mentioned the possibility of using jenkins build machines provided by the ASF. > Use Wercker instead of Travis-CI > > > Key: CALCITE-1412 > URL: https://issues.apache.org/jira/browse/CALCITE-1412 > Project: Calcite > Issue Type: Bug >Reporter: Julian Hyde >Assignee: Francis Chuang > > There are reports that Wercker is less prone to hanging when running tests > than Travis CI. We should investigate. > [~francischuang], can you attach a pull request? > Does Wercker have an equivalent of the "build status" at the top of README.md? > Also can you see whether you can re-enable JdbcTest.testExplainJoin3 (which > is disabled due to OutOfMemoryError on Travis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CALCITE-1412) Use Wercker instead of Travis-CI
[ https://issues.apache.org/jira/browse/CALCITE-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15547163#comment-15547163 ] Francis Chuang commented on CALCITE-1412: - Proposed changes: https://github.com/apache/calcite/pull/294 > Use Wercker instead of Travis-CI > > > Key: CALCITE-1412 > URL: https://issues.apache.org/jira/browse/CALCITE-1412 > Project: Calcite > Issue Type: Bug >Reporter: Julian Hyde >Assignee: Francis Chuang > > There are reports that Wercker is less prone to hanging when running tests > than Travis CI. We should investigate. > [~francischuang], can you attach a pull request? > Does Wercker have an equivalent of the "build status" at the top of README.md? > Also can you see whether you can re-enable JdbcTest.testExplainJoin3 (which > is disabled due to OutOfMemoryError on Travis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CALCITE-1412) Use Wercker instead of Travis-CI
[ https://issues.apache.org/jira/browse/CALCITE-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566947#comment-15566947 ] Francis Chuang commented on CALCITE-1412: - Integration with Wercker seems to be impossible according to INFRA as they are not able to allow write access to repos from third parities. > Use Wercker instead of Travis-CI > > > Key: CALCITE-1412 > URL: https://issues.apache.org/jira/browse/CALCITE-1412 > Project: Calcite > Issue Type: Bug >Reporter: Julian Hyde >Assignee: Francis Chuang > > There are reports that Wercker is less prone to hanging when running tests > than Travis CI. We should investigate. > [~francischuang], can you attach a pull request? > Does Wercker have an equivalent of the "build status" at the top of README.md? > Also can you see whether you can re-enable JdbcTest.testExplainJoin3 (which > is disabled due to OutOfMemoryError on Travis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
