Skip to content

Unblock SwiftPM's build #2876

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 2 commits into from
Aug 19, 2020
Merged

Unblock SwiftPM's build #2876

merged 2 commits into from
Aug 19, 2020

Conversation

neonichu
Copy link
Contributor

This fixes two issues:

@neonichu
Copy link
Contributor Author

@swift-ci please smoke test

@neonichu
Copy link
Contributor Author

./swiftpm/Utilities/build-using-self: line 16: 79151 Illegal instruction: 4 swift build -c $CONFIGURATION

This is still here, so I guess this is actually using the superior? Let's disable for now.

This fixes two issues:
- First one is the same as swiftlang#2875
- Second one is a crash related to build conditionals which looks like a
longer standing bug that was triggered by swiftlang/swift-llbuild#681
Unforunately, llbuild CI doesn't test the package, so it slipped through
and now causes SwiftPM to crash when building itself
@neonichu
Copy link
Contributor Author

@swift-ci please smoke test

@neonichu
Copy link
Contributor Author

Oh I get it now, the self-hosting bot uses the superior to build itself, so this PR can't fix it.

Copy link
Contributor

@abertelrud abertelrud left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks, Boris!

@neonichu
Copy link
Contributor Author

/home/buildnode/jenkins/workspace/swift-package-manager-Linux-smoke-test/branch-master/swiftpm/Sources/Workspace/Workspace.swift:1421:24: error: type of expression is ambiguous without more context

This might be an issue with the vendored copy of TSC not being synced up.

@abertelrud
Copy link
Contributor

Yes, most likely. You could just remove the withAuthorizationProvider thing, right?

@neonichu
Copy link
Contributor Author

Yah, but then the self-hosted bots will be broken for future PRs.

@neonichu
Copy link
Contributor Author

@swift-ci please smoke test

@abertelrud
Copy link
Contributor

Right, I just realized that. Syncing is the right way to go.

Is there a follow-on fix for llbuild here after things get unbroken (again, many thanks for your work on that!).

@neonichu
Copy link
Contributor Author

Not sure yet, I haven't looked in detail at the llbuild change and if there might be issues with it.

@neonichu
Copy link
Contributor Author

Ugh, my sync was incomplete, I forgot new files.

@neonichu
Copy link
Contributor Author

@swift-ci please smoke test

@tomerd
Copy link
Contributor

tomerd commented Aug 19, 2020

cc @compnerd

skarred14 pushed a commit to val-verde/swift-package-manager that referenced this pull request Aug 26, 2020
* Unblock SwiftPM's build

This fixes two issues:
- First one is the same as swiftlang#2875
- Second one is a crash related to build conditionals which looks like a
longer standing bug that was triggered by swiftlang/swift-llbuild#681
Unforunately, llbuild CI doesn't test the package, so it slipped through
and now causes SwiftPM to crash when building itself

* Sync TSC changes from master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants