[
https://issues.apache.org/jira/browse/KUDU-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204139#comment-17204139
]
Grant Henke commented on KUDU-2715:
-----------------------------------
A good amount of fixes have gone in recently. The remaining failing tests are:
{code}
13 - client-test.1 (Failed)
324 - kudu-tool-test.1 (Failed)
425 - trace-test (Failed)
{code}
> 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.9.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)
