You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/09/29 17:08:01 UTC

[jira] [Updated] (KUDU-2715) Get all tests passing on macOS

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

Grant Henke updated KUDU-2715:
------------------------------
    Affects Version/s:     (was: 1.9.0)
                       1.14.0

> Get all tests passing on macOS
> ------------------------------
>
>                 Key: KUDU-2715
>                 URL: https://issues.apache.org/jira/browse/KUDU-2715
>             Project: Kudu
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.14.0
>            Reporter: Adar Dembo
>            Priority: Major
>
> It seems that there are always a handful of tests that don't pass when run on macOS, though precisely which set depends on the underlying version of macOS. This taxes the release vote process, wherein macOS-based Kudu developers are forced to figure out whether the test failures they're seeing are "known issues" or indicative of problems with the release. Not to mention the day-to-day process of developing on macOS, where you never quite know whether your local work regressed a test, or whether that test was broken all along.
> In the past we looked into macOS CI builds and found the situation to be fairly bleak. Hopefully things have improved since then, but if not, I think we should still get the tests passing uniformly (disabling those which make no sense) and work in an ad hoc fashion towards keeping them that way.



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