[Mono-dev] Mono porting and splitted tests

Ian Dichkovsky ianpro at gmail.com
Mon Jan 26 09:22:37 EST 2009


Yes, I got your point.
In our case it was useful to split several crashed tests among several
Also, it was easy to get number of tests passed/failed to know how
much was done and how much was left.


2009/1/26 Zoltan Varga <vargaz at gmail.com>:
> Hi,
>  I had done mono ports to many platforms, and I didn't find this to
> be a problem. You
> can run mono using
> mono -v --regression basic.exe
> and it will print out each method as it is JIT compiled, so you can
> see which one is causing
> a crash.
>                 Zoltan
> On Mon, Jan 26, 2009 at 1:23 PM, Ian Dichkovsky <ianpro at gmail.com> wrote:
>> Hi,
>> We are now doing mono port to MIPS n32 & 64 architecture. Yes, we
>> aware of Mark Mason's efforts with the MIPS port :-)
>> During porting we came to the conclusion that single big binary test
>> sets (basic.exe, basic-long.exe, etc.) are inconvinient. On the
>> initial stage of porting, mono binary could crash in the middle of
>> testing and the rest of functions just hadn't a chance to run. These
>> crashes doesn't give us clear picture, which functions passed and
>> which failed. We splitted tests to different files, so each test
>> function has its own source and binary.
>> We think that it would be a good idea to add these splitted tests to
>> SVN. It will simplify future mono ports to the new platforms. Sources
>> available upon request.
>> Regards,
>> Ian
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list

More information about the Mono-devel-list mailing list