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:19:00 UTC

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

     [ https://issues.apache.org/jira/browse/HUDI-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

leesf reassigned HUDI-312:
--------------------------

    Assignee: leesf

> 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)