[IronPython] Interim CI server for IronPython
rjnienaber at gmail.com
Fri Feb 4 07:36:53 CET 2011
> create a new dependent build and use the Command Line runner to "build"
the tests. As long as TestRunner returns an appropriate exit code, it will
at least give an overall pass/fail, and the build log will show which
individual ones failed.
I had to use the MSBuild runner to build TestRunner and then switch to the
Command Line runner to run the tests but otherwise it
you suggested. The only downside is that updates to TestRunner won't
taken into account but I think that just has to be kept in mind. The
following tests are failing:
It seems like there are some which are build server related. I'll
investigate and see if they can be updated.
I was thinking about adding more granularity to the reporting of the tests
other than just pass/fail for all of them. Would it be worthwhile to add a
/nunitoutput option to TestRunner that would output the results in the nunit
format? It looks like TeamCity has an 'Import data from XML' option where it
could point to the output from the TestRunner.
On Thu, Feb 3, 2011 at 9:32 PM, Jeff Hardy <jdhardy at gmail.com> wrote:
> On Thu, Feb 3, 2011 at 1:40 PM, Richard Nienaber <rjnienaber at gmail.com>
> >> There's no reason that IronRuby can't be set up
> >> on teamcity.codebetter.com as well, but I'm not familiar with its
> >> build process.
> > I've added the IronRuby and DLR solutions and the DLR unit tests to the
> > build.
> It would be nice to integrate the IronPython tests, somehow, so that
> the results of those would show up as well.
> Thought: create a new dependent build and use the Command Line runner
> to "build" the tests. As long as TestRunner returns an appropriate
> exit code, it will at least give an overall pass/fail, and the build
> log will show which individual ones failed.
> - Jeff
> Users mailing list
> Users at lists.ironpython.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironpython-users