You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "leesf (Jira)" <ji...@apache.org> on 2019/10/29 07:51:00 UTC

[jira] [Comment Edited] (HUDI-312) Investigate recent flaky CI runs

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

leesf edited comment on HUDI-312 at 10/29/19 7:50 AM:
------------------------------------------------------

On no output, I changed the [travis.yaml|https://github.com/leesf/incubator-hudi/commit/dcc7e6a13b41dcf8e8df30eb8d5b64367b8feb06], borrow from [here|https://github.com/cyberFund/cybernode-archive/commit/0dbb14c5169144b7535cbf3dc474916b93a64a5e] and run more than 5 times in [travis|https://travis-ci.org/leesf/incubator-hudi/jobs/604252022], no output does not occurs again. I will continue restart the travis and observe the result before send a PR.


was (Author: xleesf):
On no output, I changed the [travis.yaml|https://github.com/leesf/incubator-hudi/commit/dcc7e6a13b41dcf8e8df30eb8d5b64367b8feb06], borrow from [here|https://github.com/cyberFund/cybernode-archive/commit/0dbb14c5169144b7535cbf3dc474916b93a64a5e] and run more than 5 times in [travis|https://travis-ci.org/leesf/incubator-hudi/jobs/604252022], no output occurs again. I will continue restart the travis and observe the result before send a PR.

> Investigate recent flaky CI runs
> --------------------------------
>
>                 Key: HUDI-312
>                 URL: https://issues.apache.org/jira/browse/HUDI-312
>             Project: Apache Hudi (incubating)
>          Issue Type: New Feature
>          Components: Testing
>            Reporter: Vinoth Chandar
>            Assignee: leesf
>            Priority: Major
>             Fix For: 0.5.1
>
>         Attachments: Builds - apache_incubator-hudi - Travis CI.pdf
>
>
> master used to be solid green. noticing that nowadays PRs and even some master merges fail with 
> - No output received for 10m
> - Exceeded runtime of 50m 
> - VM exit crash 
> We saw this earlier in the year as well. It was due to the apache org queue in travis being busy/stressed. I think we should shadow azure CI or circle CI parallely and weed out code vs environment issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)