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-11135] Swift CI: (R.swift) Swift Source Compatibility Suite (master[-debug]) #4685

Closed
xedin opened this issue Jul 15, 2019 · 3 comments
Closed
Labels

Comments

@xedin
Copy link
Member

xedin commented Jul 15, 2019

Previous ID SR-11135
Radar rdar://problem/53085717
Original Reporter @xedin
Type Bug
Status Resolved
Resolution Done
Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Bug
Assignee None
Priority Medium

md5: 23cb9ae75bc3082e3568c4a13550029d

is duplicated by:

  • SR-11136 Swift CI: (RxDataSources) Swift Source Compatibility Suite (master[-debug])

Issue Description:

Jenkins URL: https://ci.swift.org/job/swift-master-source-compat-suite/3871

/Users/buildnode/jenkins/workspace-private/swift-master-source-compat-suite/project_cache/R.swift/Sources/RswiftCore/ResourceTypes/Xcodeproj.swift:28:20: error: value of type 'ProjectFileError' has no member 'description'
        warn(error.description)
             ~~~~~ ^~~~~~~~~~~

Starting happening in build #3865 with following changes:

    AST: add a workaround for VS2017 
    Sort `DeclAttributeAndRange`s Deterministically
    AST: Remove ObjectLiteralExpr::{get,set}SemanticExpr()
    Replace all 9999 availability in non-stdlib tests. (#26109)
    Replace stdlib and test/stdlib 9999 availability. (#26108)
@beccadax
Copy link
Contributor

Between the previous job run and this one, the version of the XcodeEdit dependency suddenly changed from 2.4.1 to 2.7.1 in defiance of the Package.resolved file, which caused R.swift to fail to build. RxDataSources also had its RxSwift dependency change versions from 4.0.0 to 4.5.0, despite Package.resolved specifying 4.0.0.

Possibly related to #2230 which was checked in between those two runs and changes how Package.resolved files are interpreted. @aciidb0mb3r

@ankitspd
Copy link
Member

Reverting my commit:

5.1 #2240
master #2239

@beccadax
Copy link
Contributor

Reverting the SwiftPM commit seems to have resolved this issue. We've also reverted the XFAILs in the source compatibility suite.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants