commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [exec] Better OpenVMS testing support for sebb ....
Date Sun, 25 May 2008 21:32:43 GMT
On 25/05/2008, Siegfried Goeschl <siegfried.goeschl@it20one.at> wrote:
> Hi Sebastian,
>
>  any news regarding VMS testing - I would like to cut a release but I'm not
> sure if it is completely broken or we just have issues running a few
> regression tests ...
>

There seems to be a problem with the behaviour of process destroy on
VMS - it does not always guarantee that the process is destroyed. I
think that is a JVM bug.

Not sure how long it would to take to fix the test case to get round
this, so I suggest you go ahead with the release anyway. Perhaps the
release notes should mention that some of the unit tests don't
currently work on VMS.

>  Cheers,
>
>  Siegfried Goeschl
>
>
>  sebb wrote:
>
> > 2008/4/21 Siegfried Goeschl <sgoeschl@gmx.at>:
> >
> >
> > > Hi Sebastian,
> > >
> > >  under
> http://people.apache.org/~sgoeschl/download/commons-exec/
> you will an
> > > improved version of the test distribution - it could/should pass most of
> the
> > > test on OpenVMS .... ;-) ... can you give it a run?
> > >
> > >
> > >
> >
> > Sorry for the delay - the test server was down.
> >
> > I've fixed a couple of the test errors in SVN:
> > - the tests assumed that 0=success and 1=failure, which is not true for
> VMS
> > - VMS does not return INVALID_EXIT value if the executable is not
> > found; the test was too strict.
> >
> > There are still a couple of problems:
> >
> > 1)
> testExecuteWatchdog(org.apache.commons.exec.DefaultExecutorTest)junit.framework.AssertionFailedError:
> > Process did not create Exec
> > ute Exception when killed
> >        at
> org.apache.commons.exec.DefaultExecutorTest.testExecuteWatchdog(DefaultExecutorTest.java:206)
> >        at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >        at
> org.apache.commons.exec.TestRunner.main(TestRunner.java:47)
> > 2)
> testExecuteAsyncWithProcessDestroyer(org.apache.commons.exec.DefaultExecutorTest)junit.framework.AssertionFailedError
> >        at
> org.apache.commons.exec.DefaultExecutorTest.testExecuteAsyncWithProcessDestroyer(DefaultExecutorTest.java:331)
> >        at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >        at
> org.apache.commons.exec.TestRunner.main(TestRunner.java:47)
> >
> >
> > I think these are due to problems with Process#destroy() - it looks
> > like this does not always work on VMS.
> > I'm trying to sort this out.
> >
> >
> >
> > >  Thanks in advance
> > >
> > >  Siegfried Goeschl
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > >  To unsubscribe, e-mail:
> dev-unsubscribe@commons.apache.org
> > >  For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
>  To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>  For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message