Skip to content

[test] Re-enable very large allocation codegen test #63188

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
Jan 26, 2023

Conversation

xwu
Copy link
Collaborator

@xwu xwu commented Jan 24, 2023

A follow-up to #63034, #63093, #63110, #63095.
Hopefully this completes the saga.

Resolves rdar://104435186.

@xwu
Copy link
Collaborator Author

xwu commented Jan 24, 2023

@swift-ci test

@xwu
Copy link
Collaborator Author

xwu commented Jan 25, 2023

cc @ahoppen, @grynspan

@xwu
Copy link
Collaborator Author

xwu commented Jan 25, 2023

@shahmishal, is there any good way to test this on the AArch64 Ubuntu CI platform before merging?

@ahoppen
Copy link
Member

ahoppen commented Jan 25, 2023

AFAIK, I don’t think there is a way to test AArch64 Ubuntu it in PR testing. I wouldn’t take that for a definite answer though.

@shahmishal
Copy link
Member

We don't have aarch64 support available on PR testing right now, however we are able to trigger Apple Silicon testing if that help.

@xwu
Copy link
Collaborator Author

xwu commented Jan 25, 2023

@shahmishal I suppose it wouldn’t hurt to test, but as I understand it that wasn’t giving any trouble…

I guess otherwise since all the bots are green the strategy can only be to merge and revert if necessary?

@ahoppen
Copy link
Member

ahoppen commented Jan 26, 2023

Yes, let's merge and if it breaks bots, we will need to revert again.

@xwu xwu merged commit 4655604 into swiftlang:main Jan 26, 2023
@xwu xwu deleted the re-enable-very-large-allocation-codgen-test branch January 27, 2023 04:06
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