At long last, the current IronPython test results can be viewed on the CI server. Go to http://teamcity.codebetter.com/viewLog.html?buildId=30746&buildTypeId=bt365&tab=buildResultsDiv and then select 'login as guest'. There's currently 185 passes, 150 failures, and 177 ignored.
Many of the failures share the same root cause (doctest is broken) and many others are just one test failing that should be easy to fix. Some of the tests are ignored/disabled because they cause deadlocks, infinite loops, or StackOverflowExceptions. These aren't clearly marked, but I'll try to find somewhere to put the 'why'. Threaded runs are currently broken because the test runner will occasionally deadlock waiting for results from the tests, so always run with /threads:1 (which will be the default soon-ish). The tests don't work on Mac/Linux right now because there's too many windows-isms hardcoded in. Work is needed there. If you want to run an individual test, use `test-ipy /test:<test_name>`. You can find test_name in the IronPython.tests file to see exactly what the test does. I'm hoping this will help shine a light on some of the areas of IronPython that don't quite work as expected and get some fixes in. - Jeff _______________________________________________ Ironpython-users mailing list Ironpython-users@python.org http://mail.python.org/mailman/listinfo/ironpython-users
