dev@glassfish.java.net

Re: Quicklook failure

From: Ming Zhang <Ming.Zhang_at_Sun.COM>
Date: Thu, 03 Apr 2008 10:44:23 -0700

Sahoo,

You are right! Quicklook was failing since there was no successful build
for a while at http://kohsuke.sfbay/hudson/job/glassfish-v3/ . The first
successful build today is build #2966 (Arpil 3, 9:51:19 AM). Quicklook
just picked up that build and the tests are passing now (#174 Apr 3,
10:31:20 AM):
http://kohsuke.sfbay/hudson/job/glassfish-v3-quicklook/

Thanks,
Ming

>
>
> I have checked in a fix (r19567 [1]) this evening - no I did not cause
> the failure in the first place. Don't believe hudson's QL job. It fails
> because it is using older artifacts. Why? I think it is because the v3
> job, which is reponsible for pushing the binaries to remote repo, is
> still failing because of same old jdbc ra build issue in hudson m/c. So,
> you need to build the v3 in order to make QL pass again in your env.
>
> Thanks,
> Sahoo
>
> [1] http://fisheye4.cenqua.com/changelog/glassfish-svn/?cs=19567
>
> Sherry Shen wrote:
> >
> > The problem is shown on recent QuickLook run.
> > #172 Apr 3, 2008 9:01:37 AM
> > <http://kohsuke.sfbay/hudson/job/glassfish-v3-quicklook/172/>
> > http://kohsuke.sfbay/hudson/job/glassfish-v3-quicklook/
> > Thanks!
> >
> > Sherry
> > Jeanfrancois Arcand wrote, On 4/3/2008 9:00 AM:
> >> Salut KM :-)
> >>
> >> Kedar Mhaswade wrote:
> >>> Dinesh Patil wrote:
> >>>> JF, I tried it, still the same error.
> >>>> Jeanfrancois Arcand wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> can you try the following workaround:
> >>>>>
> >>>>> remove all $glassfish.home/modules/grizzly* (except
> >>>>> grizzly-module.jar) and see if that makes a difference? Looks like
> >>>>> we have a classloader issues somewhere...
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> -- Jeanfrancois
> >>>>>
> >>>
> >>> JFA,
> >>>
> >>> I too experience this. Any work-around available?
> >>> Want to run the QL before my changes are committed.
> >>
> >> I've checked a fresh workspace this morning and wasn't able to
> >> reproduce the problem on Linux. Is someone able to still reproduce
> >> it? The strange things is we seems to have StringManager,
> >> StringManagerTmp (???) in several package. I think it confuse the
> >> classloader...I'm looking into it as this issue comes and go since 6
> >> weeks :-)
> >>
> >> A+
> >>
> >> -- Jeanfrancois
> >>
> >>
> >>>
> >>> Thanks,
> >>> Kedar
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> >>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> >> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net For
> > additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>