-
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
What the check File.WriteAllBytes("testasm.dll", data) in tests? #30
Comments
That's weird, that line is inside a lock, so there shouldn't be any concurrent writes to that file. The line itself can be safely removed, it's here for convenience purposes so one could inspect the generated assembly with disassembler right away. |
This happens after running tests for As far as XamlX/tests/XamlParserTests/CompilerTestBase.cs Lines 124 to 126 in 697a419
($exception).FusionLog from VS debugger
It seems that this is a VS problem and it is somewhat similar to this question |
What happens if you change the file extension from |
Extension change helped 🤨 |
But it still seems to me that it is better to delete it, since it does not really carry anything, and the load on the storage exists |
Should probably wrap it inside |
Ok, I added an extra condition on build for this in #31 |
Hello!
I am thinking to add github actions and, accordingly, restore tests. I have updated the nuget packages and upgraded to netcoreapp 3.1. But the chair ran into the fact that my tests fall in this place
XamlX/tests/CecilTests/CompilerTestBase.cs
Line 60 in 697a419
With the following error
If I comment out, most of the tests pass (I don't think those test pairs are related to this). What this check?
P.S. If necessary, you can try, for example, using System.IO.Abstractions.TestingHelpers, writing something like this
The text was updated successfully, but these errors were encountered: