When we make a major effort to make IPy work with a third party package, how shall we clue you to re-enable the tests? An announcement on this forum, or what? -- Vernon
On Wed, Apr 29, 2009 at 10:55 AM, Dave Fugate <dfug...@microsoft.com> wrote: > The technical bar for inclusion of 3rd party tests into our checkin system is > pretty simple - the test process needs to emit a non-zero exit code when it > fails. When some portion of a test fails under IronPython for whatever > reason, we simply disable that portion. For example, we run around 200 > CPython 2.6 test_*.py files for every IronPython checkin with roughly a > thousand individual test cases in these modules disabled. With this in mind, > it likely doesn't matter that most of Django's test suite does not pass => we > can disable the broken stuff. > > As for inclusion of commit messages in the CodePlex source synchs, we'll look > into this. It's a bit challenging as sometimes we work on getting IronPython > running against/with the latest unannounced Microsoft technology (e.g., we > had IronPython running under Silverlight months before Silverlight was > publically announced) and this is often reflected in our checkin comments. > > Thanks, > > Dave > > _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
