Yes, I was able to reproduce the undeploy failure on my local machine.
But it seems a v3.1 bug. I let the QL stopped before undeployment and
did some debugging. After the cluster testing, the undeployment of the
apps failed in first time but if you run the same undeployment command
again, it successed. I copied the logs dir of v3.1 to here:
http://javaweb.sfbay/~mzh777/v31/ql/4802/logs/
If I comment out the cluster testing, the QL undeployment will success
in the first run. Please let me know if anyone knows the cause.
Ming
On 7/3/2010 7:40 AM, Sanjeeb Sahoo wrote:
> I am not sure if this is related to your check in, but I now see
> undeploy failing at the end of QL tests. It is there in hudson log [1]
> as well. Again I don't understand why QL has failed to detect this.
>
> undeploy-v3-impl-unix:
> [exec] Command undeploy failed.
> [exec] remote failure: A supplemental command failed; cannot
> proceed further
> [exec]
> [exec] Result: 1
>
> Looks like all app remain deployed after QL is done.
>
> [1]
> http://hudson.glassfish.org/job/gf-trunk-build-continuous/4802/consoleText
>
> On Saturday 03 July 2010 05:11 AM, Ming Zhang wrote:
>> I have just added cluster tests to QL. As of m2, the 3.1 requires to
>> set environment variable:
>> ENABLE_REPLICATION=true
>>
>> The cluster tests are now running under the default QL profile
>> against glassfish distribution. To run the cluster tests alone, you
>> can do:
>> ant -Dglassfish.home={V3 Installation Dir} all_cluster
>> at quicklook top level.
>>
>> I have updated the quicklook doc
>> (quicklook/QuickLook_Test_Instructions.html) for these info.
>>
>> Thanks,
>> Ming
>