I have no idea why the Mono test on macOS on GitHub CI fails. I have noticed though that Azure uses "Test Execution Command Line Tool Version 17.3.3 (x64)", while GitHub uses "Test Execution Command Line Tool Version 17.7.0-preview-23364-03+bc17bb9693cfc4778ded51aa0ab7f1065433f989 (x64)". Is it intentional?
Also, running Mono tests locally on 6.2.0.200 (CI is using 6.2.0.188) in debug mode fails on three tests: test_ctypes, test_memoryio_stdlib, test_namebinding (the last one is different than #1564). They all pass in release mode and they all pass on .NET in both debug and release modes.
@slozier, do those tests pass on your local machine?
I have no idea why the Mono test on macOS on GitHub CI fails. I have noticed though that Azure uses "Test Execution Command Line Tool Version 17.3.3 (x64)", while GitHub uses "Test Execution Command Line Tool Version 17.7.0-preview-23364-03+bc17bb9693cfc4778ded51aa0ab7f1065433f989 (x64)". Is it intentional?
Also, running Mono tests locally on 6.2.0.200 (CI is using 6.2.0.188) in debug mode fails on three tests:
test_ctypes,test_memoryio_stdlib,test_namebinding(the last one is different than #1564). They all pass in release mode and they all pass on .NET in both debug and release modes.@slozier, do those tests pass on your local machine?
Originally posted by @BCSharp in https://github.com/IronLanguages/ironpython3/issues/1732#issuecomment-1690525286
See also additional discussion in https://github.com/IronLanguages/ironpython3/issues/1732