Skip to content

Fix diagnoseInvalidResource #3320

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

Merged
merged 1 commit into from
Mar 8, 2021

Conversation

neonichu
Copy link
Contributor

@neonichu neonichu commented Mar 4, 2021

This changes diagnoseInvalidResource to work off the declared resources instead of the ones we found rules for. Also amended some of the tests with a check for a count of diagnostics since they could pass with zero diagnostics being emitted.

This changes `diagnoseInvalidResource` to work off the declared resources instead of the ones we found rules for. Also amended some of the tests with a check for a count of diagnostics since they could pass with zero diagnostics being emitted.
@neonichu
Copy link
Contributor Author

neonichu commented Mar 4, 2021

@swift-ci please smoke test

@neonichu
Copy link
Contributor Author

neonichu commented Mar 4, 2021

Failure looks unrelated:

/Users/buildnode/jenkins/workspace/swift-package-manager-with-xcode-self-hosted-PR-osx/branch-main/swiftpm/Tests/WorkspaceTests/WorkspaceTests.swift:4659: error: -[WorkspaceTests.WorkspaceTests testArtifactDownloadWithPreviousState] : XCTAssertEqual failed: ("[AbsolutePath:"/tmp/ws/.build/artifacts/A", AbsolutePath:"/tmp/ws/.build/artifacts/A"]") is not equal to ("[AbsolutePath:"/tmp/ws/.build/artifacts/A", AbsolutePath:"/tmp/ws/.build/artifacts/A", AbsolutePath:"/tmp/ws/.build/artifacts/B"]")

@neonichu
Copy link
Contributor Author

neonichu commented Mar 4, 2021

@swift-ci please smoke test macOS

@tomerd tomerd added the ready Author believes the PR is ready to be merged & any feedback has been addressed label Mar 5, 2021
@abertelrud abertelrud merged commit cdaaf0a into swiftlang:main Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready Author believes the PR is ready to be merged & any feedback has been addressed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants