Thanks for the link.
If breaking the test is expected, they shouldn’t be ignored of course. 
I assume test_cpp_extensions_aot_no_ninja is forcefully disabling ninja even if it’s installed, so it might be still a valid test.
I’m not familiar with MacOS, but if you cannot run all tests (and don’t have a GPU to run the whole test stack), you could use the CI for it, which would be executed in your PR for the fix.