MariaDB
MTR flag to mark tests as incompatible with macOS
Introduces a new MTR include, not_mac.inc, which when included at the top of a test, prevents that test from running on macOS.
There are many tests that don't work with macOS presently and they are not excluded in this commit; however, one is, as an example. The remaining tests will be fixed or marked as incompatible in future commits.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.
would be great to see a test that needs include/not_mac.inc, with an explanation of what's so special in mac that the test doesn't work there. Not file name case sensitivity, not mac's CrashReporter, but really, just "mac"
would be great to see a test that needs
include/not_mac.inc, with an explanation of what's so special in mac that the test doesn't work there. Not file name case sensitivity, not mac's CrashReporter, but really, just "mac"
@vuvova I devised this mechanism as a way for us to get the mac buildbot working without fixing every test first. At the same time, this would prevent new test failures from creeping in because we could make the mac builder "required" when pushing commits, preventing deliveries from introducing new mac test failures. What you're asking for seems like a diagnosis of each mac test failure that we know about. At this point, that is time consuming which meanwhile allows for more failures to appear. Is such a pragmatic approach not desired, and if so why not? In short, it would be nice to plug the holes in the hull before bailing the water out.
Hi @vuvova. A comment from @abarkov on MDEV-33652 highlights the need for this exclusion mechanism to be included sooner rather than later. In short, he'd like to wait for another fix to merge to 11.5 so that he can fix a failing macOS test in another way. (My original fix is here). I have no problem with that, but in the meantime this test will continue to fail on macOS. If the exclusion mechanism was in place, then we could leave a comment for Alex on his ticket to re-enable this failing test as part of his delivery.
Hi @DaveGosselin-MariaDB , in the meanwhile the test could be fixed not to use upper case letters in the object names.
@DaveGosselin-MariaDB my point was that this particular test, and, I suspect many mac-specific failures could be covered by include/have_case_insensitive_fs.inc. That is, the question was what tests fail not just on case insensitive file system but on mac because of its inherent macness ?
Hi @vuvova , ah I understand now. There's nothing about inherent 'macness' that breaks this test. The test in question could be fixed either by @abarkov 's suggestion or yours (to use include/have_case_insensitive_fs.inc). I will fix it and others having case-sensitivity issues (full list on MDEV-33616 ) in either of those two ways, as context permits. Thanks for the feedback.