Re: help needed for building a release repository test

> Hi Jerome,
>
> unfortunately, I'm not qualified at all to help you.
> I know nearly
> nothing about MC1. You may want to ask to Colin
> Putney, Avi Bryant.
> Why not asking the mailing list directly?
>
> I'm sorry
>
> 2007/7/16, Jerome Peace
> <[hidden email]>:
> > Damien Cassou [hidden email]
> >
> >
> > Hi Damien I am asking for your help in building a
> > release repository test.
> >
> > At least twice, something has been saved in the
> > repository that has caused the corresponding
> changeset
> > to show up empty.
> >
> > When I pointed that out and Edgar attempted to fix
> > 7109 the wrong files with the correct names got
> into
> > the repository and things came to an impass for a
> > while.
> >
> > I want to have a test that will check an entire
> > repository and report back if it has internal
> > consistency or not.
> >
> > I am a MC avoider so I wanted, if your willing, to
> > enlist your help to determine how to write such a
> > test.
> >
> > What needs to be looked for and what needs to be
> > compared to certify that a repository is
> consistant
> > and complete?
> >
> > I want a comprehensive test and an incremental
> one.
> >
> > The comprehensive one makes few (no) assumptions
> about
> > what changed.
> >
> > The incremental one could assume that everything
> was
> > alright before the most recent change and just
> check
> > to see if the most recent changes screwed things
> up.
> >
> > This will help catch problems early and allow them
> to
> > remain managable.
> >
> > Ultimately I want to create a fresh repository,
> find
> > the way to muck things up and catch the errors.
> And
> > keep doing this until I understand things.
> >
> > Advice and/or code would be wonderful.
> >
> > Yours in curiosity and service, --Jerome Peace
>