Successful tests keep spamming "One or more child tests had errors"
IDE: JetBrains Rider 2024.3.4 Build #RD-243.23654.126, built on January 19, 2025
Runtime version: 21.0.5+8-b631.30 amd64 (JCEF 122.1.9)
Windows 10.0
.NET Core v8.0.11 x64 (Server GC)I'm building a project with Godot v4.4-beta1, using C# and writing it in Rider.
For Unit Testing, I selected NUnit 3.14.0, (other dependencies below). While it was frustrating initially, I eventually got it to run decently with Continuous Testing, and all seems well.
Except, the console output window, stdout/stderr or whatever this is, it keeps spamming the same message over and over. There are no errors to my understanding, so what is causing this?
There are 22 of them in total. I'm not sure why 22 exactly, because I only have 1 test fixture, and 1 test function, and I removed all of the Assert calls in hopes that it might change something - give me a clue. and 1 test function, and I removed all of the Assert calls in hopes that it might change something—give me a hint.
I'm completely lost here; I can't find any ‘verbosity’ settings, and I'm supposing others like me who found this are just ignoring it.
I'm not launching a Godot instance - I'm running pure .NET C# here. I disabled NativeAOT.
Main Project Dependencies:
<PackageReference Include="FluentResults" Version="3.16.0"/>
<PackageReference Include="MessagePack" Version="3.1.1"/>
<PackageReference Include="Microsoft.Extensions.Logging.Abstractions" Version="9.0.1"/>
<PackageReference Include="Sentry" Version="5.0.0"/>
<PackageReference Include="Sentry.Profiling" Version="5.0.0"/>
<PackageReference Include="Serilog" Version="4.2.1-dev-02337"/>
<PackageReference Include="Superpower" Version="3.0.0"/>Testing Project Dependencies:
<PackageReference Include="coverlet.collector" Version="6.0.0"/>
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.8.0"/>
<PackageReference Include="NUnit" Version="3.14.0"/>
<PackageReference Include="NUnit.Analyzers" Version="3.9.0"/>
<PackageReference Include="NUnit3TestAdapter" Version="4.5.0"/>Please sign in to leave a comment.
Hello Xevion,
Thank you for contacting Rider support.
From first look it looks like an output of your test. Would you mind checking if that text prints to output if you run it from the terminal?
If not, and this output is only being printed in Rider, I would appreciate it if you could share Rider logs:
Have a nice day!
Hi Dmitry,
Yes, I confirmed that
dotnet testdoes not output anything like what I'm plagued with. This time, there are 51 instances; it seems like the longer I do testing in my project, the more errors occur. Or maybe it has something to do with assertion count? Very hard to say.I completed the Trace and uploaded the log bundle just now.
Thank you!
Hello Xevion,
Thank you for the details shared! I reproduced the issue and registered this bug to our tracker. Please watch the issue for further updates: RIDER-122560 One or more child tests had errors Exception doesn't have a stacktrace in green tests.
I found the following workaround: (you can find recording that demonstrates workaround on the issue page)
Close the Continuos Testing tab in the Tests tool window:
Launch another Continuous Testing session, so the new tab appears:
Note: the same workaround applies to the common unit tests session (you can do the same with any tab in Tests explorer).
Hope that helps. Have a nice day!
Awesome, that works; can confirm that it doesn't seem to be printing in the log a bunch.
Thanks.
Hmm, it's not a full workaround, but it does clear the log spam at the time you open/close the tab. But it doesn't persist, further errors will add additional logs.
Have a nice day!