Re: Build python-HP_UX-B.11.00-9000_829-taylor was successful.

Anders Qvist <[email protected]> Tue, 16 Jul 2002 22:56:50 +0200
Newsgroups gmane.comp.python.snake-farm.user
Message-ID <[email protected]>
On Tue, Jul 16, 2002 at 11:55:42AM -0400, Guido van Rossum wrote:
> > >>>>> "SF" == sfarmer  <[email protected]> writes:
> > 
> >   SF> Build all succeded. Any warnings are appended below.  -- cc:
> >   SF> "../python/dist/src/Objects/listobject.c", line 2025: warning
> >   SF> 562: Redeclaration of "list_iter" with a different storage class
> >   SF> specifier: "list_iter" will have internal linkage.  
> > 
> > Is there any chance that this build is not running with a current CVS
> > checkout?  I thought I fixed this problem several days ago.
> 
> You didn't. :-(
> 
> You changed the forward declaration from 'staticforward' to 'static'.
> But the actual function definition doesn't have a 'static' keyword.
> I'll fix this.
> 
> > In general, it would be helpful to see some metadata about the CVS
> > checkout.  I'm not sure what -- the date of the checkout, the output
> > of the checkout/update command.
> 
> Agreed.

The next step will be to add a parser that collates the build reports
to a summary. In order to do this, I will store data in a relational
database. Eventually, that database should be able to drive a website
to present data that can answer these things.

Also, it is in the TODO to store the list of files that gets updated
each time we synch with SF CVS. It exists in the cvs_master.sh

     files=`$cvs -q update`
     # FIXME: Save the files list
     if test `echo "$files" | grep "^[CPUMA]" | wc -l` -gt 0; then
         echo "- module was modified"
	 modified="yes"
     fi

... but isn't kept. Storing this list would help us keep track of what
actually change from build to build. 

> > Thirdly, are these tests running against the trunk or a branch?
> > Ideally, we could get test runs of the trunk and of the
> > release22-maint branch.  The trunk helps us work on the next release;
> > the maintainance branch helps us fix bugs that are causing problems
> > for users of the current release.

Currently, each machine can only do one build, since module name and
uname info is used to differentiate them. We will want to change this
so that we can have multiple versions. This is a perfect project if
you want to contribute to the Snake Farm, as it can be developed and
tested on any UNIX box.

-- 
Anders "Quest" Qvist

"We've all heard that a million monkeys banging on a million typewriters
will eventually reproduce the entire works of Shakespeare. Now, thanks 
to the Internet, we know this is not true." -- Robert Wilensky