Xcode 16.1 beta (and Slather 2.8.4) - Failed to load coverage: unsupported instrumentation profile format version
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- ruby
- Domain
- testing-qa
Research direction
Start by examining how Slather loads the attached Coverage.profdata and how it invokes Xcode coverage tools; the issue provides the failing format-version error but names no source file or test. Compare behavior on Xcode 16.1 beta CI and local Apple Silicon, then identify a reproducible input and test path. Done means Slather can process the affected coverage profile or reports the incompatibility clearly.
Written by the indexing model from the issue text.
Description
I recently updated to Slather 2.8.4 to fix the Xcode 16 compatibility issue.
Using Xcode 16.1 beta, It works well locally, so thank you for that :)
But when running in CI (Azure DevOps), I get the following error
Slathering...
error: Failed to load coverage: '/Users/runner/Library/Developer/Xcode/DerivedData/Assets-cecsqcpehsibqugchwzmtqbbxlil/Build/ProfileData/21543275-1377-4AC5-82B2-8929738D1C83/Coverage.profdata': unsupported instrumentation profile format version
error: Could not load coverage information
Slathered
I've attached the Coverage.profdata file, but I'm not sure what else I can do to investigate the issue. If there is anything else I can provide to help, please let me know.
One possible reason is the Azure DevOps build agent is an Intel mac and I'm running on Apple Silicon locally. This previously worked fine with Xcode 15.
- Dominant language
- Ruby
- Stars
- 1.6k
- Forks
- 239
- Avg merge
- 10h 19m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SlatherOrg/slather
-
2.8.6: NoMethodError "undefined method 'first'" in profdata_coverage_dir whenever --scheme is usedPossibly taken @MirekNalepa claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
SlatherOrg/slather#586 · 3 comments · 4 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
SlatherOrg/slather#582 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
SlatherOrg/slather#580 · 9 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 56/100
SlatherOrg/slather#578 · 3 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
SlatherOrg/slather#577 ·
All issues in SlatherOrg/slather
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
ETQ admin, le select de condition d'une annotation répétable liste les champs publics deux foisOpen
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
demarche-numerique/demarche.numerique.gouv.fr#14301 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
voxpupuli/puppet-powerdns#251 ·
-
needs verification
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days