Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Remove dependency on `RemoteExecutor` in tests
See original GitHub issueProblem description:
RemoteExecutor has been used in a number of tests for the sole purpose of enabling visual styles. However RemoteExecutor has proven to be rather unstable (see: https://github.com/dotnet/arcade/issues/5325).
The tests have been update to run with visual styles on by default in https://github.com/dotnet/winforms/pull/4197, however RemoteExecutor hasn’t been cleaned out.
We need to scan the codebase for RemoteExecutor (and "_Skip = "Crash with AbandonedMutexException. See: https://github.com/dotnet/arcade/issues/5325"_") and update those tests, removing RemoteExecutor.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@willibrandon I’m assigning this to you. Please holler if you won’t be able to work on it.
That’d be great!
We use/tried to use
RemoteExecutorfor situations where we need change the global state (e.g., disable visual styles, control the clipboard, the mouse or the keyboard, etc.). Because unit tests are run in parallel any changes to the global state destabilises the whole suite. So one way of resolution is to migrate the RE-dependent tests to the UIIntegration test project that executes tests serially and can bootstrap each test as necessary without risks of affecting other tests.