Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.14.0
-
None
-
None
Description
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.