tag:help.appveyor.com,2012-11-13:/discussions/problems/6499-test-fail-with-no-explanationAppVeyor: Discussion 2018-08-25T02:16:42Ztag:help.appveyor.com,2012-11-13:Comment/423858582017-04-19T19:05:12Z2017-04-19T19:05:12ZTest fail with no explanation<div><p>Machine is not out of resources. I cloned your repository and reproduced build error. When I connect to build worker with <a href="https://www.appveyor.com/docs/how-to/rdp-to-build-worker/">RDP</a>, I see normal load until this exception thrown. At that moment 1 of 2 CPU Cores is being totally occupied by Windows Error Reporting (werfault) and the following message appears in Application log:<br></p>
<pre>
<code>Faulting application name: nunit-agent.exe, version: 3.6.1.0, time stamp: 0x58bdfcf4
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x00007ff90381e8d6
Faulting process id: 0x694
Faulting application start time: 0x01d2b93bd74be517
Faulting application path: C:\Tools\NUnit3\nunit-agent.exe
Faulting module path: unknown
Report Id: 5efba4f1-252f-11e7-817b-00155d20c03a
Faulting package full name:
Faulting package-relative application ID:</code>
</pre>
Which means that it is stack overflow in <code>nunit-agent.exe</code>. I tried previous nunit versions and also using command line with <code>--workers=1</code> setting. Nothing helps.
<p>I wonder if it works locally for you from command line. And if yes, what specific command do you run and what specific nunit version do you use?</p>
<p>Ilya.</p></div>Ilya Finkelshteyn