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
Currently 32 bit test execution is only done for .NET Framework, with dotnet xunit which is an obsolete tool today, we need to adapt dotnet test, and add 32 bit CI targets for both net5.0 and netcoreapp3.1. Opening an issue to remember and track this debt.
We don't do, but IMO we should. 32bit is still relevant and memory + runtime behavior is different there. Runtime deviations between 32bit and 64bit are less common these days, so no need to replicate all the configurations, but having at least one 32bit CI leg would be nice.
A follow up on #1378 (comment).
Currently 32 bit test execution is only done for .NET Framework, with
dotnet xunit
which is an obsolete tool today, we need to adaptdotnet test
, and add 32 bit CI targets for bothnet5.0
andnetcoreapp3.1
. Opening an issue to remember and track this debt.See:
https://twitter.com/tannergooding/status/1316755685938393089
The text was updated successfully, but these errors were encountered: