-
Notifications
You must be signed in to change notification settings - Fork 55
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/benchmarks failing #33
Comments
Why this happens is described here #31 (comment) In fact, conditionally, they work. But they need to be fixed so that they really work
I did not understand why this is happening, perhaps windows OS does not have time to release dll files, but this was decided in #31, since this strut is not needed for batch tests
Also, it affects dotnet test. I have a hunch that if you select what netstandard was for, then the problems in VS will disappear |
"Ghost" tests in VS test explorer is a Visual Studio bug. |
Okey. It looks like to do this, we will need to rewrite the tests to separate the test asserts from the classes dotnet test trying run for testclasses... https://github.com/rstm-sf/XamlX/runs/1270736821?check_suite_focus=true#step:5:36 |
It seems to me that these are problems test runner |
I do not see any particular problem in separating classes from tests. See https://github.com/rstm-sf/XamlX/actions/runs/313556568 |
It works now #35 Thus, it remains to figure out the following
|
An example that this is most likely a dotnet test problem |
Line 1 in 697a419
|
@grokys tests in VS looks good https://github.com/rstm-sf/XamlX/tree/refactor/extract_netstandard_tests |
Also solves the problem of non-building Benchmarks |
This is mentioned in #30 but that has been closed: the test and benchmarks suite currently does not run. I can see the following problems in a freshly cloned repro:
File.WriteAllBytes("testasm.dll", data)
throws (What the check File.WriteAllBytes("testasm.dll", data) in tests? #30)CompilerTestBase.GetCallbacks
fails on net47:CecilTests
/CecilNetstandardTests
are being built fornetstandard2.0
which is not a valid TFM for unit tests due to it being an API not a platform causing the tests to show up in the VS test explorer but not be runnableThe text was updated successfully, but these errors were encountered: