Skip to content

Move wasm queue to one that has more capacity and condition it #39373

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
Jul 15, 2020

Conversation

safern
Copy link
Member

@safern safern commented Jul 15, 2020

This new queue has v8 and more capacity, so remove the workaround and run the tests when libraries or mono are changed.

Fixes: #39238
Fixes: #38400

cc: @akoeplinger @steveisok @MattGal @directhex

@Dotnet-GitSync-Bot
Copy link
Collaborator

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@ghost
Copy link

ghost commented Jul 15, 2020

Tagging subscribers to this area: @safern, @ViktorHofer
Notify danmosemsft if you want to be subscribed.

@safern
Copy link
Member Author

safern commented Jul 15, 2020

Merging since the only affected build (Browser) is green.

@safern safern merged commit 64c9e7c into dotnet:master Jul 15, 2020
@safern safern deleted the wasm-newhelixqueue branch July 15, 2020 20:54
@karelz karelz added this to the 5.0.0 milestone Aug 18, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
4 participants