-
-
Notifications
You must be signed in to change notification settings - Fork 889
Enable support to use libgdiplus library on macOS #1403
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
Closed
Closed
Changes from all commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
bb55ac8
add "macos-latest" to build matrix
antonfirsov 5d4cf9e
try installing "mono-libgdiplus"
antonfirsov 525fdbd
add "shell: bash"
antonfirsov 0f076c8
try 'macos-10.15'
antonfirsov f087dee
try ${{matrix.options.os}}
antonfirsov 921aa06
next hack to try
antonfirsov ff14733
if: startsWith(matrix.options.os, 'macos')
antonfirsov 95dfbd0
Merge remote-tracking branch 'origin/af/macos-ci' into af/macos-libgd…
AlexNDRmac eb7e80f
Add Nuget cache, improve build matrix
AlexNDRmac fe06e3b
Add support using libgdiplus on macOS
AlexNDRmac e587161
Fix incompatible package reference for OSX
AlexNDRmac 8527b2c
Revert syntax for workflow, move osx package to build targets
AlexNDRmac 902fbaa
Remove setup netcore action
AlexNDRmac 3fc0b60
Disable nuget packages cache
AlexNDRmac 734aca2
Do not run windows specific tests on macOS
AlexNDRmac a4bf8b7
Decorate OSX specific tests
AlexNDRmac 9e27be8
Merge branch 'master' into af/macos-libgdiplus-fix
JimBobSquarePants c06de77
Enable nuget cache, rework redundant shell for all steps
AlexNDRmac fd7a759
Declare powershell in unix way
AlexNDRmac 2855437
Save actual output of Images for failed CI runs
AlexNDRmac 2af8cba
Merge branch 'master' into af/macos-libgdiplus-fix
JimBobSquarePants 0b35db8
Merge branch 'master' into af/macos-libgdiplus-fix
antonfirsov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JimBobSquarePants reminder to ourselves that we shall open an issue for the disabled tests when this gets merged.
@AlexNDRmac I suppose you work on Mac. Can you help us by posting the output images saved by these tests on your machine? (
tests/Images/ActualOutput/ResizeTests/ResizeFromSourceRectangle_Rgba32_CalliphoraPartial.png). Same for the other 2 disabled tests.Expected images are under
tests/Images/External/ReferenceOutput/ResizeTests/if interested.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I propose to use save-action and fail scenario. For example: tests on mac failed, then starts build step with condition 'on-fail' and save any details (pictures, logs... etc) as build artifacts. Next, you can download it for investigation :)
I can add this scenario to workflow, it's very simple and useful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds awesome, let's give it a try!
I wonder though what's simplest: here or in a separate PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do the tests not fail locally or something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, better - is separate PR, because this improvement not related to
libgdiplus.On my Mac some tests failed, but on CI such tests - passed :) I use 10.14.16, but CI using 10.15.x.... and on my Mac some tests kills some dotnet sub-processes... It's very interesting case, maybe I can foud whick component have "magic" influence on tests, but experiments requires some time.