Crash on MacOS `15.4`

[mr-fixit]

📄 Using coverage file: /Users/vagrant/git/mobile-scripts/coverage.xml
Invalid memory access (signal 11) at address 0x20
[0x104dffca0] ?? +4376755360 in /opt/homebrew/Cellar/coveralls/0.6.15/bin/coveralls
[0x104dff768] ?? +4376754024 in /opt/homebrew/Cellar/coveralls/0.6.15/bin/coveralls
[0x1853b7624] _sigtramp +56 in /usr/lib/system/libsystem_platform.dylib
[0x18e9a8e14] xmlSAX2AttributeDecl +360 in /usr/lib/libxml2.2.dylib (2 times)

[afinetooth]

UPDATE: Description of issue

macOS 15.4+ changed Apple’s system libxml2, which can crash Crystal-based tools that link against it. We’re publishing a new Homebrew build that links to Homebrew’s libxml2 instead. In the meantime, please run your job on macos-14 or on ubuntu-latest.

Duplicate of: coverallsapp/github-action#248

---

@mr-fixit thanks for the heads up. We've received three (3) such reports since yesterday and are pretty sure it relates to this:

• Segfault when using XML module on MacOS 15.4 crystal-lang/crystal#15619

All reports so far entail using coverage-reporter to upload XML-format coverage reports.

[afinetooth]

@mr-fixit (and anyone else affected), we think there's a workaround to this right now:

Workaround:

• Roll-back your CI runner from MacOS 15.4 to 15.2.

We have reports that coverage-reporter works as expected on 15.2.

If that's not the case for you, please let us know here.

[afinetooth]

@mr-fixit I changed the title of this issue to be slightly more accurate since it's not the version of coverage-reporter, but the version of MacOS that's the issue right now. Hope you don't mind.

The point in making the distinction is so users don't waste time downgrading to 0.6.14, which will not resolve the issue if they stay on MacOS 15.4 (since the issue comes from using the system-installed xml library). If anyone discovers otherwise, please let us know!

[jpmckinney]

This occurs for me on 15.5 on GitHub Actions as well. I don't see a way to select a minor version of macos: https://docs.github.com/en/actions/how-tos/write-workflows/choose-where-workflows-run/choose-the-runner-for-a-job

[agronholm]

Seems like the bug was fixed upstream. Would it be possible to get a fix here too? Or let us know how to select a different minor version of the macos runner, @afinetooth ?

[afinetooth]

@agronholm I'm afraid I was wrong before—I'm not aware of a way to select a minor version for a runner and the latest MacOS runners (macos-15-*) still appear to be running 15.5 per this README:

macOS 15
OS Version: macOS 15.5 (24F74)
Kernel Version: Darwin 24.5.0
Image Version: 20250811.2170

Do you need macos-15? If not, you can specify any available pre-15 macos- runner.

We hope to get to this, this week. Do you happen to have a link re: that upstream fix, and whether that's in MacOS, or Homebrew?

[agronholm]

@agronholm I'm afraid I'm not aware of a way to select a minor version for a runner and the latest MacOS runners (macos-15-*) still appear to be running 15.5 per this README:

macOS 15
OS Version: macOS 15.5 (24F74)
Kernel Version: Darwin 24.5.0
Image Version: 20250811.2170

Do you need macos-15? If not, you can specify any available pre-15 macos- runner.

We hope to get to this, this week. Do you happen to have a link re: that upstream fix, and whether that's in MacOS, or Homebrew?

Thanks. I misspoke when mentioning "upstream" because I followed the issue link at the top, but they did have a potential clue here. Not sure if that's helpful or not.

[afinetooth]

@agronholm Ah, I see, so maybe upstream in Crystal.