Samsa wrapper provides jdk/bin/java wrapper, but it does not affect jdk/bin/jre/java launcher, mentioned below. So, any changes in samsa wrapper should not affect running jdk/jre/bin/java launcher.
However, I see similar intermittent problems occurred in jdktools CC/CI runs with starting jdk/bin/jrasigner.exe and jdk/bin/keytool.exe processes, which are implemented by samsa wrapper and thus are affected by recent changes in HARMONY-4190. However, I cannot reproduce these failures. The problem may be in a system environment used for CC/CI runs. I'd suggest to reboot these machines and check if this solves the problem. If not, you can revert changes made in HARMONY-4190 and see if this helps. Thanks. Ivan On 6/22/07, Gregory Shimansky <[EMAIL PROTECTED]> wrote:
Vladimir Ivanov wrote: > Hello, > yesterday I tried to run CLASSLIB tests over HDK and found that now > the command like (jre java): > ant test -Dbuild.module=archive -Dtest.jre.home=<>\trunk\target\hdk\jdk\jre > > leads to the message in the log: > -get-test-vm-output: > [exec] Execute failed: java.io.IOException: CreateProcess: > trunk\target\hdk\jdk\jre\bin\java -version error=193 > > test-jre-vm-info: > [echo] hy.test.vm.name = ibm > > while command like (jdk java): > ant test -Dbuild.module=archive -Dtest.jre.home=<>\trunk\target\hdk\jdk > > works OK: > -get-test-vm-output: > > test-jre-vm-info: > [echo] hy.test.vm.name = drl > > As I remember launcher was updated some time ago. > Could someone take care about this issue? There was also a patch to samsa wrapper which is executed as jdk/jre/bin/java.exe I think. Take a look at HARMONY-4190, it is possible that patches from it caused this behavior. -- Gregory
