[
https://issues.apache.org/jira/browse/KUDU-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570279#comment-17570279
]
Marton Greber edited comment on KUDU-2715 at 7/23/22 9:22 AM:
--------------------------------------------------------------
Intel macs, 98.2% passed:
{code:java}
188 - security-itest (Failed)
243 - external_mini_cluster-test (Failed)
260 - rpc-test.2 (Failed)
265 - rpc-test.7 (Failed)
343 - kudu-tool-test.0 (Failed)
345 - kudu-tool-test.2 (Failed)
346 - kudu-tool-test.3 (Failed)
446 - trace-test (Failed) {code}
ARM macs ( with patch:
[https://gerrit.cloudera.org/#/c/9652/|https://gerrit.cloudera.org/#/c/18770/]
) 98% passed:
{code:java}
170 - memory_gc-itest (Failed)
188 - security-itest (Failed)
243 - external_mini_cluster-test (Failed)
327 - cbtree-test (Failed)
343 - kudu-tool-test.0 (Failed)
344 - kudu-tool-test.1 (Failed)
345 - kudu-tool-test.2 (Failed)
346 - kudu-tool-test.3 (Failed)
446 - trace-test (Failed){code}
was (Author: JIRAUSER290256):
Intel macs, 98.2% passed:
{code:java}
188 - security-itest (Failed)
243 - external_mini_cluster-test (Failed)
260 - rpc-test.2 (Failed)
265 - rpc-test.7 (Failed)
343 - kudu-tool-test.0 (Failed)
345 - kudu-tool-test.2 (Failed)
346 - kudu-tool-test.3 (Failed)
446 - trace-test (Failed) {code}
ARM macs ( with patch: [https://gerrit.cloudera.org/#/c/9652/] ) 98% passed:
{code:java}
170 - memory_gc-itest (Failed)
188 - security-itest (Failed)
243 - external_mini_cluster-test (Failed)
327 - cbtree-test (Failed)
343 - kudu-tool-test.0 (Failed)
344 - kudu-tool-test.1 (Failed)
345 - kudu-tool-test.2 (Failed)
346 - kudu-tool-test.3 (Failed)
446 - 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.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.20.10#820010)
