Skip to content

Conversation

@dsyme
Copy link
Contributor

@dsyme dsyme commented Nov 10, 2016

This fixes #1728 and makes sure we are checking the error code.

This PR also removes the exclude option from build.cmd which was causing batch file hell (because of the use of a ! character!), which was only used to exclude Expensive tests. Now use an explicit include Expensive.

build.cmd Outdated
set command="%_dotnetexe%" "%~dp0tests\testbin\!BUILD_CONFIG!\coreclr\fsharp.core.unittests\FSharp.Core.Unittests.dll"
if '%TEST_CORECLR_COREUNIT_SUITE%' == '1' (
REM these copies should not be needed, see https://github.com/fsharp/fsharp/issues/642
xcopy /S /Q /Y src\fsharp\FSharp.Core.Unittests\bin\!BUILD_CONFIG!\netcoreapp1.0\* "%~dp0tests\testbin\!BUILD_CONFIG!\coreclr\fsharp.core.unittests\"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@KevinRansom This is the explicit copy

@dsyme dsyme merged commit 0e40f7d into dotnet:master Nov 10, 2016
@dsyme
Copy link
Contributor Author

dsyme commented Nov 10, 2016

Thanks to @enricosada for helping to work out how to use FsCheck. See fsharp/fsharp#642 which was causing problems

@dsyme
Copy link
Contributor Author

dsyme commented Nov 10, 2016

@KevinRansom When I merged this I thought that the "part 2" .NET Core tests were passing. Instead the changes means that the pre-existing "missing DLL" failure is now being recorded as an actual failure.

@KevinRansom
Copy link
Contributor

I'm actually working on nugetising this.

@dsyme
Copy link
Contributor Author

dsyme commented Nov 11, 2016

@KevinRansom great

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

For .NET Core, the FSharp.Core.Unittests are not running correctly

3 participants