Skip to main content

Testing waithandles in MSTest

For a client I needed to write a parallel execution mechanism that executes multiple tasks at the same time on different threads but further execution had to wait before all threads signals complete. In this situation, synchronization becomes very important,  so I used the WaitHandle classes to implement this functionality. As no code is complete without good unit tests, I added a test to validate the behavior of the waithandles:

   1:  [TestMethod]
   2:  public void Waithandle_Should_Wait_Until_All_Tasks_Complete()
   3:  {    
   4:     Action task1 = ()=> DoSomething();
   5:     Action task2 = ()=> DoSomething();
   6:     Action task3 = ()=> DoSomething();
   7:   
   8:     IAsyncResult result1= task1.BeginInvoke(null, null, null);   
   9:     IAsyncResult result2= task2.BeginInvoke(null, null, null);   
  10:     IAsyncResult result3= task3.BeginInvoke(null, null, null);      
  11:   
  12:     WaitHandle.WaitAll(new WaitHandle[]{result1.AsyncWaitHandle, result2.AsyncWaitHandle, result3.AsyncWaitHandle});     
  13:     // Asserts go here...
  14:  }


In this example,  WaitHandle.WaitAll stops any further execution until all tasks complete.


The only problem is that when you try to run this test, it fails with the following error message: Test method Ordina.ParallelRunner.Waithandle_Should_Wait_Until_All_Tasks_Completethrew exception:  System.NotSupportedException: WaitAll for multiple handles on a STA thread is not supported..


This is actually documented behavior on the part of WaitHandle.WaitAll. It seems that MSTest runs in an STA by default.


Fortunately, this is configurable and can be edited in your .testrunconfig file. There's no user interface for this setting, so you will have to open the file and  add this line to make MSTest run in an MTA.

   1:  <ExecutionThread apartmentState="1" />

By default, the value of this element is 0 (which is equivalent to ApartmentState.STA - the default value of the enumeration), but as you can see, I've changed it to 1 (which is equivalent to ApartmentState.MTA). After saving this change, the test now succeeds.

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...