[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] gdb for testing on hudson
|
Doug or Vivian, can you extend the build timeout on Hudson to 180 minutes?
Thanks
> -----Original Message-----
> From: Marc Khouzam
> Sent: Thursday, January 10, 2013 1:25 PM
> To: 'CDT General developers list.'
> Subject: RE: [cdt-dev] gdb for testing on hudson
>
> Things are looking better now, but the new tests make
> the build longer than the configured built time limit.
>
> I don't have permissions to change that value.
>
> Doug, can you set the hudson job to only time out
> after 180 minutes?
>
> Thanks
>
> > -----Original Message-----
> > From: Marc Khouzam
> > Sent: Thursday, January 10, 2013 6:46 AM
> > To: CDT General developers list.
> > Subject: RE: [cdt-dev] gdb for testing on hudson
> >
> > It was pointed-out to me that we are trying to build 32bit
> > apps (-m32) with a 64bit lib.
> > I will try to remove the -m32 to see if that helps. I'm not
> > entirely sure why we force -m32.
> > ________________________________________
> > From: cdt-dev-bounces@xxxxxxxxxxx
> > [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Marc Khouzam
> > [marc.khouzam@xxxxxxxxxxxx]
> > Sent: January 9, 2013 11:51 PM
> > To: CDT General developers list.
> > Subject: Re: [cdt-dev] gdb for testing on hudson
> >
> > Looks like there is a problem with libstdc++. The errors are below:
> >
> > [INFO] --- maven-antrun-plugin:1.3:run (prepare) @
> > org.eclipse.cdt.tests.dsf.gdb ---
> > [INFO] Executing tasks
> >
> > makeTestApps:
> > [exec]
> > /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-l
> > inux/bin/ld: skipping incompatible
> > /usr/lib64/gcc/x86_64-suse-linux/4.3/libstdc++.so when
> > searching for -lstdc++
> > [exec]
> > /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-l
> > inux/bin/ld: skipping incompatible
> > /usr/lib64/gcc/x86_64-suse-linux/4.3/libstdc++.a when
> > searching for -lstdc++
> > [exec]
> > /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-l
> > inux/bin/ld: cannot find -lstdc++
> > [exec] collect2: ld returned 1 exit status
> > [...]
> > [exec] make: *** [all] Error 1
> > [exec] Result: 2
> >
> > Also, Iooking at the Makefile that builds the test
> > applications, we'll need to modify it because
> > it also requires GDB to be in the path. For convenience here
> > is the Makefile from cdt.tests.dsf.gdb/data/launch/src/Makefile
> >
> > src = $(wildcard *.cc *.c)
> > destDir = ../bin
> > GCCFLAGS = -gdwarf-2 -pthread -m32
> >
> > all:
> > @mkdir -p $(destDir)
> > # Name the target with an .exe extension so that CVS does not
> > # include it when making a patch
> > @for file in $(src) ; \
> > do \
> > target=`basename $$file .c` ; \
> > target=`basename $$target .cc` ; \
> > g++ $(GCCFLAGS) $$file -o
> $(destDir)/$$target.exe ; \
> > done
> > # Now generate the core file that we need for the post-mortem
> > core-file tests
> > @gdb --nx --batch -ex "b testLocals" -ex run -ex
> > "next 16" -ex "gcore ../bin/core" \
> > ../bin/ExpressionTestApp.exe > /dev/null
> >
> > ________________________________________
> > From: cdt-dev-bounces@xxxxxxxxxxx
> > [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Doug Schaefer
> > [dschaefer@xxxxxxx]
> > Sent: January 9, 2013 4:41 PM
> > To: CDT General developers list.
> > Subject: Re: [cdt-dev] gdb for testing on hudson
> >
> > OK, got gdb hooked up to the tests and the try to run. But it
> > looks like they all fail. Any thoughts?
> >
> > https://hudson.eclipse.org/hudson/me/my-views/view/CDT/job/cdt
> > -maint/364/testReport/
> >
> > D
> >
> > From: Doug Schaefer <dschaefer@xxxxxxx<mailto:dschaefer@xxxxxxx>>
> > Reply-To: "CDT General developers list."
> > <cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>>
> > Date: Friday, 4 January, 2013 1:44 PM
> > To: "cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>"
> > <cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>>
> > Subject: Re: [cdt-dev] gdb for testing on hudson
> >
> > Got side tracked a little by an ugly scanner discovery bug
> > but will get to this right after.
> >
> > :D
> >
> > Sent from my BlackBerry 10 smartphone.
> >
> > From: Marc Khouzam
> > Sent: Friday, January 4, 2013 1:04 PM
> > To: 'CDT General developers list.'
> > Reply To: CDT General developers list.
> > Subject: Re: [cdt-dev] gdb for testing on hudson
> >
> >
> >
> > Hi Doug,
> >
> > any success about this?
> >
> > Thanks
> >
> > Marc
> >
> > > -----Original Message-----
> > > From:
> > cdt-dev-bounces@xxxxxxxxxxx<mailto:cdt-dev-bounces@xxxxxxxxxxx>
> > > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
> > > Sent: Thursday, December 20, 2012 11:49 AM
> > > To: CDT General developers list.
> > > Subject: Re: [cdt-dev] gdb for testing on hudson
> > >
> > > On 12-12-20 11:44 AM, "Marc Khouzam"
> > > wrote:
> > >
> > > >
> > > >> -----Original Message-----
> > > >> From:
> > cdt-dev-bounces@xxxxxxxxxxx<mailto:cdt-dev-bounces@xxxxxxxxxxx>
> > > >> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
> > > >> Sent: Thursday, December 20, 2012 11:25 AM
> > > >> To: CDT General developers list.
> > > >> Subject: Re: [cdt-dev] gdb for testing on hudson
> > > >>
> > > >> That only holds for that shell, not the maven job.
> > > >>
> > > >> I don't mind adding a property. Do know off hand where this
> > > >> check is made?
> > > >
> > > >The name of the gdb binary to be used is set in:
> > > >org.eclipse.cdt.tests.dsf.gdb.framework.BaseTestCase#setGdbPr
> > > ogramNamesLau
> > > >nchAttributes()
> > > >
> > > >Thinking about it, using a property would allow people to
> > > leave their PATH
> > > >alone and use the property themselves.
> > >
> > > Definitely a positive side effect of this.
> > >
> > > >
> > > >Another option that was suggested to me was to have maven
> > > download the
> > > >pre-built
> > > >gdb from some location. This would make the solution
> > > slave-independent.
> > > >But
> > > >where to store this gdb so it could be downloaded...
> > >
> > > All slaves can see our staging directory where the final bits
> > > are placed
> > > so that should be safe.
> > >
> > > >
> > > >The property sounds like a quick and good solution.
> > > >
> > > >Thanks for taking care of this!
> > >
> > > No problem. We need to step up our involvement in this to
> > > make sure our
> > > user base is happy with our common debugger experience.
> > >
> > > >
> > > >Marc
> > > >
> > > >>
> > > >> On 12-12-20 11:20 AM, "Marc Khouzam"
> > > >> wrote:
> > > >>
> > > >> >Thanks Doug!
> > > >> >
> > > >> >As you mention, the JUnit tests look for gdb in PATH. The
> > > >> name of GDB
> > > >> >must include the version.
> > > >> >If you installed gdb 7.5 or 7.5.1, gdb must be named gdb.7.5
> > > >> >
> > > >> >How about adding a build step in Hudson to "Execute shell"
> > > >> and set the
> > > >> >PATH variable?
> > > >> >
> > > >> >Marc
> > > >> >
> > > >> >
> > > >> >
> > > >> >________________________________
> > > >> >
> > > >> > From:
> > cdt-dev-bounces@xxxxxxxxxxx<mailto:cdt-dev-bounces@xxxxxxxxxxx>
> > > >> [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> > > >> >On Behalf Of Doug Schaefer
> > > >> > Sent: Thursday, December 20, 2012 11:04 AM
> > > >> > To: CDT General developers list.
> > > >> > Subject: [cdt-dev] gdb for testing on hudson
> > > >> >
> > > >> >
> > > >> > This is mainly for Marc but I'm sure others are
> interested too.
> > > >> >
> > > >> > I've *finally* got gdb built so that it can run on the
> > > >> Eclipse servers.
> > > >> >They run SuSE linux which is just different enough to make
> > > >> it complicated.
> > > >> >
> > > >> > At any rate, how do I now integrate it into our build?
> > > >> Setting the path
> > > >> >is going to be complicated in Hudson. Do we have a property
> > > >> I can set to
> > > >> >point at it? Should we add one?
> > > >> >
> > > >> > Thanks!
> > > >> > :D
> > > >> >
> > > >> >_______________________________________________
> > > >> >cdt-dev mailing list
> > > >> >cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>
> > > >> >https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > > >>
> > > >> _______________________________________________
> > > >> cdt-dev mailing list
> > > >> cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>
> > > >> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > > >>
> > > >_______________________________________________
> > > >cdt-dev mailing list
> > > >cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>
> > > >https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > >
> > > _______________________________________________
> > > cdt-dev mailing list
> > > cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>
> > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > >
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
