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

[Wasm] Stand up AOT CI Leg #46633

Closed
steveisok opened this issue Jan 6, 2021 · 3 comments
Closed

[Wasm] Stand up AOT CI Leg #46633

steveisok opened this issue Jan 6, 2021 · 3 comments
Assignees
Labels
Milestone

Comments

@steveisok
Copy link
Member

Since we were able to get System.Buffers to succeed, let's add a new CI leg to see how the rest of the suites hold up.

I would recommend starting the work out as a draft PR as there will likely be many hiccups.

@ghost
Copy link

ghost commented Jan 6, 2021

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Since we were able to get System.Buffers to succeed, let's add a new CI leg to see how the rest of the suites hold up.

I would recommend starting the work out as a draft PR as there will likely be many hiccups.

Author: steveisok
Assignees: mdh1418
Labels:

arch-wasm, area-Infrastructure-mono

Milestone: -

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Jan 6, 2021
@steveisok steveisok removed the untriaged New issue has not been triaged by the area owner label Jan 6, 2021
@SamMonoRT SamMonoRT added this to the 6.0.0 milestone Jun 23, 2021
@SamMonoRT
Copy link
Member

@mdh1418 - didn't we address this already, can we close the issue ?

@steveisok
Copy link
Member Author

Yes, this can be closed.

@ghost ghost locked as resolved and limited conversation to collaborators Jul 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants