This is the mail archive of the
mailing list for the Archer project.
Re: Compile/Test of archer-tromey-python branch
- From: Daniel Jacobowitz <drow at false dot org>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Rick Moseley <rmoseley at redhat dot com>,Project Archer <archer at sourceware dot org>
- Date: Thu, 4 Dec 2008 11:02:52 -0500
- Subject: Re: Compile/Test of archer-tromey-python branch
- References: <4937F0C2.firstname.lastname@example.org> <email@example.com>
On Thu, Dec 04, 2008 at 08:55:52AM -0700, Tom Tromey wrote:
> Rick> Yesterday afternoon I pulled the archer-tromey-python branch, compiled
> Rick> it and did a "make check". Here are the ending results I see from
> Rick> this:
> Rick> Are these failures to be expected?
> I don't know offhand how many failures there normally are.
> The gdb test suite doesn't usually have 0 FAILs. So, you generally
> have to do regression tests -- run the unmodified gdb and then the
> patched gdb and compare.
> We've been pretty lax about running the test suite on the python
> branch :-(. For the time being, just don't worry about it. I'll deal
> with the regressions once I'm done being sick.
When I built Debian packages from that branch a week ago, I saw about
60 failures on my desktop and 25 in the build environment (probably
due to having other Ada, Obj-C, Fortran, Java compilers installed).