Re: [RFA] ARI fix: Remove asprintf in breakpoint.c

Joel Brobecker
2007-10-08T16:25:09Z

> > Concerning the overnight running of testsuites
> > with different patches, does anyone have some
> > script that automates this?
>
> No - but it's reasonable to test them together in a single test run,
> I think.

That's indeed what I meant. However, I can see the need for a script
if you have to do two runs (one before patching, and one after).
I have a set of scripts that I can send, but they are deeply
dependent on my entire environment (including the interactive shell
sessions). My scripts are pretty complex because I re-use them in
many different contexts on 3 different sites (in Paris, in New York,
and at my home). Unless someone else can share a script, I think it'll
be simpler for you to write a script of your own.

The essence of my script is:

- Take patch name from argument lists.
Verify that patch exists before continuing. Nothing worse than having
a failure 12hours later because you mistyped your patch name :)

- mkdir test-dir
- cd test-dir
- cp -R gdb-sources .
- cd gdb-sources
- configure
- make
- cd gdb/testsuite
- make check
- cp gdb.sum gdb.sum.ref
- cp gdb.log gdb.log.ref
- cd ..
- patch -p0 < your-patch
- make
- cd testsuite
- make check

(with various checks against $? at the end of steps such as the
GDB build, so that you don't continue if something failed).

As I said, if the stream of your patches is relatively small,
I don't mind doing the testing for you, since it's pretty automated
on my side. But if you are going to contribute a regular amount
of patches, it makes sense to invest the time in them.

--
Joel