Conversation
Good idea, but looks like that succeeded despite the reported failure on 15.4. I'm assuming that the GH action runners are not updated yet, making this less useful. I'll have to check if there is any other downside to enabling this (I recall macOS runners had lower limits?) but if there are no downsides happy to enable it for extra coverage. |
|
I ended up adding this on the libpg_query side, where I think this matters most: pganalyze/libpg_query@e46bdf8 Unless you think there is a chance there will be macOS and Ruby-specific issues, I'd prefer we don't add more test runs here (since Linux and macOS Ruby builds are sufficiently similar). |
|
Per the earlier note, I'll close this, because I think its sufficient if we test this within libpg_query, as done above. FWIW, I suppose one could argue that some of the extconf.rb logic in pg_query is macOS-specific, but that has been pretty stable on macOS, so I don't think that alone necessitates adding macOS runners here. |
|
Sounds good, sorry for the slow reply. Thanks for your ongoing work. |
2 participants
This should provide coverage of ARM-based MacOS, e.g. for issues like #327.