runtime: Test failed: System.Runtime.Serialization.Formatters.Tests.EqualityExtensions.IsEqual

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 34 (34 by maintainers)

Commits related to this issue

Most upvoted comments

Okay 6.0.1 is out, and published on the mono-project.com preview repos. It’s not in the stable repos, and probably won’t be for a while. Give it a try, see if it fixes the bug you’re experiencing.

Current plan is to ship a release tomorrow, after running the current state of master through static analysis and fuzzing. It’s a big release.

directhex@breakfast:~/Projects/libgdiplus$ git diff 5.6.1..master | diffstat | tail -1
 180 files changed, 74237 insertions(+), 16271 deletions(-)

@safern / @danmosemsft I’m not 100% sure I understand the question I’ve been CC’ed to answer, but if we’re talking test execution, there’s basically three things we need to do to get changes everywhere:

  • If the OS that needs LibGDIPlus is docker-based (or we want to make it so) - can just update the dockerfile and make a PR to pick up the changed image.
  • If it’s a VM in our Azure VM Scale Sets - We need to update the way we install libgdiplus via PR to these machines and roll it out when possible (lately we’ve been blocked on rollouts with lockdowns followed by only 2-3 days until the next lockdown)- this may take a week or two.
  • If it’s an on-premises machine: The process is similar to the scale set version with the option to manually update the machines as a stopgap while waiting for rolling out.

Ping me on teams to chat further.

I’m not sure that building libgdiplus would be a productive use of my time. I wasn’t able to quickly discern how to build for armhf, and even if I did, I’m not sure that’s the appropriate way to come up with a version to use for the CI system - not to mention that we should be testing with libraries that are available to our users, given that it is used by System.Drawing.Common.