Hi Weldon, You've got wrong impression somehow, ehwa and cunit tests have absolutely no relation and/or dependency. Currently cunit tests are part of the top-level joint target "test", but I have no idea why there is no standalone target for them.
Another point, do your tests really fit into unit testing concept? If they involve several components, maybe just put them into different suite? 2007/5/9, Weldon Washburn <[EMAIL PROTECTED]>:
On 5/9/07, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > > Hi Weldon, > > Looks like you can't do exactly what you want with current build > scripts. Or at least I don't know an easy way. I suppose we can add a > top-level target like thread.test for running these tests separately > if you think it makes sense. How soon can thread.test be added? It turns out that I need to be able to call gc_force_gc() from jthread.lib. The cunit.test fails because jthread.lib hits an unresolved external reference (gc_force_gc) when linking with the cunit test framework. This should be an easy thing to fix once the build/test cycle is shortened. The current build/test cycle for "build ehwa.test" is more than 20 minutes currently. Looking at the big picture, what did the original test developers do to solve the above problems? Maybe this code has already been developed and simply not yet donated?? Does anybody know? Regards, > > 2007/5/8, Weldon Washburn <[EMAIL PROTECTED]>: > > All, > > From "build test2" output, it looks like cunit.test is called > (indirectly) > > by ehwa.test. "build ehwa.test" works fine but takes a really long time > to > > run. I would like to quickly run just the tests located in the > > working_vm/vm/tests/unit/thread directory. Can the build experts give > > suggestions on how to do this. > > > > Thanks > > > > -- > > Weldon Washburn > > > -- > Alexei Zakharov, > Intel ESSD > -- Weldon Washburn
