Muted tests inside Docker show as failed — using artifact-mounted mytest.dll via docker-compose

Hello TeamCity community,

I previously posted about muted xUnit tests still showing as failed when run inside a Docker container with the docker runner (using docker exec myContainer dotnet test /mytest.dll). I no longer have access to that account and am reopening the issue from a new account. Below I summarize the original context and add additional details about my current pipeline.
 

Problem

• Tests that are muted in TeamCity still show up as failed when I run them inside a Docker container using: docker exec myContainer dotnet test /mytest.dll
• I expect TeamCity to mark muted tests as muted/ignored, not failed.

My build setup in short (additional details)

• The pipeline has three build steps:
  1. Unpack artifacts from another build and copy the extracted mytest.dll into the path expected by my Docker setup. (S the mytest.dll comes prebuilt form the other build)
  2. Run docker-compose to build/prepare containers. As part of this, mytest.dll is mounted into the test container (via a bind mount or volume configured in docker-compose).
  3. Start test execution with: docker-Runner and exec-Command and “myContainer dotnet test /mytest.dll” as additional arguments
• Important: mytest.dll is not built on the same build agent; it comes exclusively as an artifact from a different build and is mounted into the container after docker-compose is started.

From the previous thread I was kinda confused about the following statements:

Add a dotnet build step (either inside or outside the Docker container) to ensure the DLL is freshly generated.

As described, the DLL comes as artifact from another build

Build the DLL outside the container, then mount the output directory into the container at runtime. 

Which I do already, as described above.

Avoid copying my.dll from previous builds or artifacts unless it has been rebuilt, as this can prevent proper test tracking in TeamCity.

Every time I run the test pipeline, I always fetch a freshly built mytest.dll from the build chain. The mytest.dll copied from the artifact is never reused between runs, so it should not break TeamCity’s test tracking.

Here is also the link of the previous thread

If there’s any other information I can provide that might help diagnose this (aside from the full build log, which I need to check before posting), please let me know.