-
Notifications
You must be signed in to change notification settings - Fork 264
[Linux] Enable build IDs. #496
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
Conversation
@swift-ci Please test |
29a0547
to
d403fc5
Compare
@swift-ci Please test |
@swift-ci Please test Windows platform |
d403fc5
to
a8aec35
Compare
@swift-ci Please test |
@swift-ci Please test Windows platform |
a8aec35
to
174a04b
Compare
@swift-ci Please test |
@swift-ci Please test Windows platform |
We should use build IDs on Linux so that we can identify the built artefacts, and also so that we can match them up with debug information should we choose to separate it. rdar://130582882
174a04b
to
9512507
Compare
@swift-ci Please test |
@swift-ci Please test Windows platform |
The macOS failure suggests that there's some configuration issue with the XCTest tests:
(The "built for macOS 14.2 which is newer than running OS" part suggests that maybe the wrong deployment target is being used here.) |
The Windows failure seems to be a failure to fetch the sources from git. |
@swift-ci Please test Windows platform |
I don't think we generally expect corelibs-xctest to work on macOS. In the past, we've discussed removing the macOS job from CI. |
I guess I can't merge this in that case, because the macOS platform test is marked as "Required". // @briancroom @grynspan |
We should use build IDs on Linux so that we can identify the built artefacts, and also so that we can match them up with debug information should we choose to separate it.
rdar://130582882