-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Fix broken symlinks for expected images on WSL #25792
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
Conversation
Check for WSL2 and WSL1 Cleanup
Thanks for this! Is there any documentation on the reported uname in WSL? |
Good question! The best I can find is microsoft/WSL#4555, so I added a check for WSL1 as well. |
ceed678
to
aa0cda7
Compare
Thanks all, cleaned that up a bit. FYI, on Windows 10, platform.uname().release returns |
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 can confirm that this is broken in WSL as stated and fixed with this change.
…792-on-v3.7.x Backport PR #25792 on branch v3.7.x (Fix broken symlinks for expected images on WSL)
PR summary
On WSL for image comparison tests, when placing the expected image in the results_images folder, symlinks are broken when accessing those images afterwards via the Windows interface. The symlink command does not fail, so the error logic does not catch it and we need to add a check for this special case.
Before, when opening an *-expected.png file:

After, the image opens correctly.
PR checklist