Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-15233] Compiler error exit: Could not read serialized diagnostics file: error("Invalid diagnostics signature") #57555

Open
josephlord opened this issue Sep 23, 2021 · 2 comments
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself

Comments

@josephlord
Copy link

Previous ID SR-15233
Radar None
Original Reporter @josephlord
Type Bug

Attachment: Download

Environment

Building with Xcode Version 13.0 (13A233) on an M1 Mac mini.

Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Bug
Assignee None
Priority Medium

md5: 259977d9ea7f5749acdf24ec873f0e00

Issue Description:

Build is failing (and it may well be erroneous code that it is calling out but I've been told that any nonzero exit is considered a bug. Apologies about the general code quality this is just a play project to explore Async Await and Core data mostly.

/Users/josephlord/hf/ios/Experiments/UKCovidData/UKCovidData/DataUseCase.swift:191:59: error: invalid conversion from throwing function of type '() throws -> Void' to non-throwing function type '() -> Void' let areas = try await context.perform { ^ /Users/josephlord/Library/Developer/Xcode/DerivedData/UKCovidData-drdmvbkbpkkgdfehcwkhtvhkjryt/Build/Intermediates.noindex/UKCovidData.build/Debug-iphonesimulator/UKCovidData.build/Objects-normal/arm64/UKCovidDataApp.dia:1:1: warning: Could not read serialized diagnostics file: error("Invalid diagnostics signature") (in target 'UKCovidData' from project 'UKCovidData') Command CompileSwift failed with a nonzero exit code

@typesanitizer
Copy link

that any nonzero exit is considered a bug

This isn't correct. If the compiler or debugger crashes, that is a bug. When there are errors, the compiler should be exiting with a non-zero exit code.

@josephlord
Copy link
Author

Sorry. Feel free to close if this is expected behaviour. I did resolve compilation (I think by extracting as a method.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself
Projects
None yet
Development

No branches or pull requests

2 participants