Skip to content

Using xcodebuild's -skipMacroValidation gives unclear results #52

@czottmann

Description

@czottmann

xcsift 1.0.23.

When macros were changed and have approvals pending, xcsift will correctly report that, and mark the output as "status: failed", which is good:

❮ xcodebuild test -scheme "Listening Post" -destination "platform=macOS" 
status: failed
summary:
  errors: 2
  warnings: 0
  failed_tests: 0
  linker_errors: 0
errors[2]{file,line,message}:
  "/Users/czottmann/Library/Developer/Xcode/DerivedData/Listening_Post-egmhdlujnlujagfxqhuwzgrpivyu/SourcePackages/checkouts/swift-case-paths/Package@swift-6.0.swift:PACKAGE-TARGET:CasePathsMacros",null,Macro “CasePathsMacros” from package “swift-case-paths” was changed since a previous approval and must be enabled before it can be used
  "/Users/czottmann/Library/Developer/Xcode/DerivedData/Listening_Post-egmhdlujnlujagfxqhuwzgrpivyu/SourcePackages/checkouts/swift-dependencies/Package.swift:PACKAGE-TARGET:DependenciesMacrosPlugin",null,Macro “DependenciesMacrosPlugin” from package “swift-dependencies” was changed since a previous approval and must be enabled before it can be used

However, when I used xcodebuild's -skipMacroValidation flag while testing, the macro errors disappear (as they should) but the run is still marked as "status: failed", which is confusing my LLM to no end:

❮ xcodebuild test -scheme "Listening Post" -destination "platform=macOS" -skipMacroValidation
status: failed
summary:
  errors: 0
  warnings: 0
  failed_tests: 0
  linker_errors: 0

Thanks for xcsift! 💛

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions