-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests in master failing due to MissingMethodException #237
Comments
Pull requests cause our tests to be run on AppVeyor. The most recently completed pull request is #214. The head of the branch for that PR was commit 69d82c3. The tests in that commit were run by AppVeyor, and they all passed. On that commit, the four tests fail when I run them locally on the command line. In both cases, the tests were run with the Microsoft Test Execution Command Line Tool. The versions were slightly different though:
|
The tests still pass on AppVeyor, which is still using version 16.5.0 of the command line tool. |
Now I locally ran the tests with version 15.9.1 of the command line tool, and four tests still fail for me. So, the issue is probably not the command line tool. |
Another difference between me and AppVeyor is the version of the Microsoft Build Engine.
|
Here are some minimal tests to help isolate the issue.
The issue has something do with the function Hedgehog.Experimental targets .NET Standard 2.0. The documentation for .NET Standard lists .NET Framework as being compatible with .NET Standard 2.0, but then tempers that by saying
It appears that a recent version of MSBuild (between 16.5.0 and 16.6.0) has introduced one such issue. This issue doesn't exist for me when targeting .NET Framework 4.7.2 (as well as 4.7.1 actually) as well as all versions of .NET Core that successfully compile. |
Happy to see you're investigating. Unfortunately I have no chance to look into this or anything else this week. |
…h_constant Replaced calls to Range.exponential with Range.constant to avoid issue #237
I don't know how to specify that the code be build with MSBuild 16.5. However, I do know how to pick the .NET Core SDK though, which has some effect on the version of MSBuild.
Furthermore, here are all the versions of .NET Core SDK 3.1. There are no versions between the two I tested. |
PR #240 implemented an acceptable workaround of this issue, and now I am also satisfied with my investigation of it (which might be of help to others). |
There are four tests in
master
failing because due to aMissingMethodException
.Below I have included the full test detail summary for all four tests. I am troubleshooting this issue now. I will comment again soon with more information.
The text was updated successfully, but these errors were encountered: