423435 - Create reference file set for Minotaur and put it in version control

Status: RESOLVED WONTFIX

(Mozilla Localizations :: Other, defect)

Description

[Axel Hecht [:Pike]]

We need a set of reference files to run Minotaur against, and a version controlled hosting.

This is needed for bug 516228, and for Firefox 3 release in general.

Rob, are there any preferences in term of version control. We made a call on a naming scheme and stuff a while back, in bug 393070. http://mxr.mozilla.org/mozilla/source/testing/release/minotaur/ it was, in configs. Any rationale for changing that?

If we go for the versioning scheme mentioned there, we may need to add support for that to Minotaur, Clint?

Comment 1

[Tim Riley [:timr]]

Clint- you and tracy have this one, right?

Comment 2

[Tracy Walker [:tracy]]

Clint has a set of ref files for Windows and Mac that we collected last week.

Comment 3

[cmtalbert]

(In reply to comment #0)
> This is needed for bug 516228, and for Firefox 3 release in general.
Axel really means bug 416228 there, not some futuristic bug from 2010. :-)
> 
> Rob, are there any preferences in term of version control. We made a call on a
> naming scheme and stuff a while back, in bug 393070.
> http://mxr.mozilla.org/mozilla/source/testing/release/minotaur/ it was, in
> configs. Any rationale for changing that?
I don't think we should change it, though I would update it.  Back then we thought of going with a scheme of config/locale/version.  But I think in email and offline we later decided that it should be: config/<os>/<version>/<locale>, so I'll propose a patch with that structure.
> 
> If we go for the versioning scheme mentioned there, we may need to add support
> for that to Minotaur, Clint?
That was discussed a long time ago and we decided against it (because we didn't want to block development on the development of this repository).  So, for by-hand runs, it's pretty simple to check these out by hand, or a script can be provided for that.  For buildbot runs, it will be easy to have buildbot check out configs as a prior step to running minotaur.

Patch forthcoming...

Comment 4

[cmtalbert]

(In reply to comment #3)
> Patch forthcoming...
> 
Um...I can't seem to make cvsdo run recursively, and this is a huge directory structure we're adding.

So, I'll attach a zip file with the config directory on down for perusal.

If that looks ok to folks, then I'll check it into the tree.

Comment 5

[cmtalbert]

Ok, plan B.  Bugzilla won't let me attach anything that big.  So the zipfile is hosted here:

http://people.mozilla.org/~ctalbert/config.zip

Let me know if you have any objections to the structure.

Comment 6

[cmtalbert]

Oops.  I checked in those files and forgot to close this bug.
http://mxr.mozilla.org/mozilla/source/testing/release/minotaur/configs/
--> RESOLVED FIXED (as I checked in the files to "fix" it).

Comment 7

[Axel Hecht [:Pike]]

Hrm. When I talked to joduinn, he wanted to have Minotaur in a state that it creates a successful testrun to get it into builds. These references go up to b4, and will more or less consistently fail against rc1+, so I guess we should either have this bug still open, or a follow up bug to actually create, and implement, a maintainance scheme for these files. In other words, get a reference for Firefox 3 in, which may still be evolving.

Do these reference files handle any protocol handlers yet?

Comment 8

[Axel Hecht [:Pike]]

Tracy, mind detailing what your VERIFIED implies here?

Comment 9

[Tracy Walker [:tracy]]

Axel, I verified that the files are checked in as we created them.  Please reopen this or create a new bug if there are issues you feel haven't been addressed here.

Comment 10

[cmtalbert]

(In reply to comment #7)
> Hrm. When I talked to joduinn, he wanted to have Minotaur in a state that it
> creates a successful testrun to get it into builds. These references go up to
> b4, and will more or less consistently fail against rc1+, so I guess we should
> either have this bug still open, or a follow up bug to actually create, and
> implement, a maintainance scheme for these files. In other words, get a
> reference for Firefox 3 in, which may still be evolving.
I think that if we do a current run of the b5 locales we'd have a pretty stable set of reference files to work from. (The checked in files are b4 and earlier).

> Do these reference files handle any protocol handlers yet?
> 
No, these were all from snapshots before the protocol handler stuff landed.

Hmmm...should we reopen this bug then?

Comment 11

[Axel Hecht [:Pike]]

Yeah. This apparently didn't block fx3, but we're not at the point where we have a reference to run automated tests against.

Reopening and clearing blocking-firefox3?.

Comment 12

[Axel Hecht [:Pike]]

Minotaur ran into a wall in the maze and died.