Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[iOS] System.Tests.PosixSignalRegistrationTests: RemoteExecutor is not supported on this platform. #55328

Closed
MaximLipnin opened this issue Jul 8, 2021 · 5 comments · Fixed by #55333
Assignees
Milestone

Comments

@MaximLipnin
Copy link
Contributor

MaximLipnin commented Jul 8, 2021

A couple of tests, added recently in #54136, fail with the following:

System.PlatformNotSupportedException : RemoteExecutor is not supported on this platform.]]>
   at Microsoft.DotNet.RemoteExecutor.RemoteExecutor.Invoke(MethodInfo method, String[] args, RemoteInvokeOptions options, Boolean pasteArguments)
   at Microsoft.DotNet.RemoteExecutor.RemoteExecutor.Invoke(Action`1 method, String arg, RemoteInvokeOptions options)
   at System.Tests.PosixSignalRegistrationTests.SignalHandlerCalledForRawSignals(PosixSignal s)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
  • System.Tests.PosixSignalRegistrationTests.SignalHandlerCalledForRawSignals
  • System.Tests.PosixSignalRegistrationTests.SignalHandlerCalledForKnownSignals

cc @steveisok

@dotnet-issue-labeler
Copy link

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

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Jul 8, 2021
@steveisok
Copy link
Member

@MaximLipnin can you check if the tests you reference feature detect for RemoteExecutor?

@MaximLipnin
Copy link
Contributor Author

@MaximLipnin can you check if the tests you reference feature detect for RemoteExecutor?

No, they don't, I'll open a PR to update the tests with [ConditionalTheory(typeof(RemoteExecutor), nameof(RemoteExecutor.IsSupported))]

@stephentoub
Copy link
Member

I will take care of it. I'm currently editing all these files.

@ghost
Copy link

ghost commented Jul 8, 2021

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

A couple of tests, added recently in #54136, fail with the following:

System.PlatformNotSupportedException : RemoteExecutor is not supported on this platform.]]>
   at Microsoft.DotNet.RemoteExecutor.RemoteExecutor.Invoke(MethodInfo method, String[] args, RemoteInvokeOptions options, Boolean pasteArguments)
   at Microsoft.DotNet.RemoteExecutor.RemoteExecutor.Invoke(Action`1 method, String arg, RemoteInvokeOptions options)
   at System.Tests.PosixSignalRegistrationTests.SignalHandlerCalledForRawSignals(PosixSignal s)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
  • System.Tests.PosixSignalRegistrationTests.SignalHandlerCalledForRawSignals
  • System.Tests.PosixSignalRegistrationTests.SignalHandlerCalledForKnownSignals

cc @steveisok

Author: MaximLipnin
Assignees: -
Labels:

area-Infrastructure-mono, untriaged

Milestone: -

@stephentoub stephentoub self-assigned this Jul 8, 2021
@steveisok steveisok removed the untriaged New issue has not been triaged by the area owner label Jul 8, 2021
@steveisok steveisok added this to the 6.0.0 milestone Jul 8, 2021
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jul 8, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jul 9, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Aug 8, 2021
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants