-
-
Notifications
You must be signed in to change notification settings - Fork 852
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
Some (28) tests are failing on master branch #1442
Comments
thanks for reporting this. I see the reason for the bitmap tests failing: Its a DebugGuard which ensures the Spans are the same length when converting to Bgra32. This is sometimes not the case during quantization where it can happen that the source is smaller then the destination. I will fix that. |
Just FYI there seem to be also an |
Is it a 32bit run? OOM-s are not extraordinary if so. AccessViolationException is a serious concern, what test is that? Is it sporadic or deterministic? |
What’s the stack trace of the AccessViolationException. I’ve seen that one pop up a few times during CI and it’s always Magick.NET |
yes the AccessViolationException is related to Also its this image: |
It's sporadic, I will put the stacktrace next time I face it. Regarding the OOM, they appear with Any CPU, x86 and x64 but it's also something quite sporadic. Here is the stacktrace:
|
Thank you @antonfirsov |
Prerequisites
DEBUG
andRELEASE
modeDescription
On a clean master branch, running all tests from VS 2019, I end up with 28 failing tests (see image below):
System Configuration
The text was updated successfully, but these errors were encountered: