The first test timed out in 30 mins. The 2nd test seems to be just blocked.
[INFO] ------------------------------------------------------- [INFO] T E S T S [INFO] ------------------------------------------------------- [INFO] Running org.apache.geronimo.testsuite.deployment.Ear13Test [INFO] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1,800.63 sec <<< FAILURE! [INFO] Running org.apache.geronimo.testsuite.deployment.Ear14Test Cheers Prasad On 9/28/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Sounds like its going to timeout hitting the war pages... --jason On Sep 28, 2006, at 3:01 PM, Prasad Kashyap wrote: > The selenium tests on windows blocks. Firefox does not open. > > I now have 5 java processes running. > > [INFO] ------------------------------------------------------- > [INFO] T E S T S > [INFO] ------------------------------------------------------- > [INFO] Running org.apache.geronimo.testsuite.deployment.Ear13Test > > Cheers > Prasad. > > On 9/28/06, Jason Dillon <[EMAIL PROTECTED]> wrote: >> On Sep 28, 2006, at 2:28 PM, Prasad Kashyap wrote: >> > Thanx for the response Jason. >> > >> > Please see if the attached components.xml is good for our new >> > "integration-test" custom packaging. >> > http://rifers.org/paste/show/1855 >> >> Hi Prasad, I have already committed the new packaging and hooked up >> the deployment-testsuite to use it. >> >> >> > If we used the m-m-p to invoke child poms, won't they inherit the >> > goals from their parents ? If they do, then won't start-server and >> > stop-server be also executed ? >> >> You will notice there is is a "child" profile in each *-testsuite >> module and that the m-m-p sets this profile to be active on executed >> child modules. This was done specifically to avoid children picking >> up the start-server/stop-server configuration from their parent. >> >> --jason >> >> >>
