IronLanguages / IronLanguages/ironpython3
GC related tests failing on Mono
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the additional discussion in issue #1732 and the related context in #1564, then reproduce the Mono debug failures in test_ctypes, test_memoryio_stdlib, and test_namebinding. Compare the GitHub and Azure test execution tool versions and Mono versions; done means the cause is identified and the three tests pass consistently in the affected CI configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100