-
Notifications
You must be signed in to change notification settings - Fork 341
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
Skip the remote executor tests #7321
Skip the remote executor tests #7321
Conversation
using Xunit.Sdk; | ||
|
||
namespace Microsoft.DotNet.RemoteExecutor.Tests | ||
{ | ||
public class RemoteExecutorTests | ||
{ | ||
[Fact] | ||
[Fact(Skip = "Remote executor is broken in VS test explorer")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does this not disable it from normal console execution?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is that even possible?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its only possible by basically rewriting swaths of xunit to make a custom Fact attribute.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought runtime did this all the time using some kind of extension pattern. Just seems like perma-skip = never run and I understand they pass outside of VS.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Runtime has a huge swath of custom fact stuff that I don't think we want to duplicate just to deal with these handful of tests. :-)
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
#7092