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

[mono] Reenable tests for #63746. #69646

Merged
merged 1 commit into from
May 25, 2022
Merged

[mono] Reenable tests for #63746. #69646

merged 1 commit into from
May 25, 2022

Conversation

vargaz
Copy link
Contributor

@vargaz vargaz commented May 21, 2022

No description provided.

@ghost ghost assigned vargaz May 21, 2022
@dotnet-issue-labeler
Copy link

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.

@vargaz
Copy link
Contributor Author

vargaz commented May 21, 2022

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vargaz vargaz requested a review from lambdageek May 22, 2022 10:06
@vargaz vargaz marked this pull request as ready for review May 22, 2022 10:06
@vargaz
Copy link
Contributor Author

vargaz commented May 22, 2022

/azp run runtime-extra-platforms

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vargaz vargaz changed the title [mono] Reenable tests to see if 63746 is fixed. [mono] Reenable tests for #63746. May 22, 2022
@vargaz vargaz requested a review from fanyang-mono May 25, 2022 12:44
@vargaz
Copy link
Contributor Author

vargaz commented May 25, 2022

Failures are unrelated.

@vargaz vargaz merged commit 3c875e5 into dotnet:main May 25, 2022
@vargaz vargaz deleted the reenable-63746 branch May 25, 2022 15:23
@ghost ghost locked as resolved and limited conversation to collaborators Jun 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants