You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. Not actually sure if this is a bug or an intentional change. When upgrading from 3.16.1 to 3.1.7.0, every NLog call started appearing in our TravisCI build output, when previously this would only show up for failing tests. This dramatically increases the output for us, and we've reverted the upgrade for now. Is this intended?
NUnit and NUnit3TestAdapter versions
NUnit 3.12.0, NUnit3TestAdapter 3.17.0
Visual Studio edition and full version number (see Help About)
N/A
A short repro, preferably attached or pointing to a git repo or gist
Hi. Not actually sure if this is a bug or an intentional change. When upgrading from 3.16.1 to 3.1.7.0, every NLog call started appearing in our TravisCI build output, when previously this would only show up for failing tests. This dramatically increases the output for us, and we've reverted the upgrade for now. Is this intended?
NUnit and NUnit3TestAdapter versions
NUnit
3.12.0
, NUnit3TestAdapter3.17.0
Visual Studio edition and full version number (see Help About)
N/A
A short repro, preferably attached or pointing to a git repo or gist
What .net platform and version is being targeted
.NET Core 3.1
If TFS/VSTS issue, what version, hosted, on-premises, and what build task you see this in
N/A
The text was updated successfully, but these errors were encountered: