461190 - Update Production 1.9 Unittests to run a11y tests suite

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: [checked in] Master.cfg patch

Currently there are many discrepancies between the repo version and the currently-used version of the master.cfg and mozbuild.py

I would like to be able to use cvs repo version of master.cfg and mozbuild.py and so am attaching patches that do the needed clean up.

The mozbuild.py patch removes stale environment settings, replaces .pl with .py on some commands and also adds the a11y test commands

The master.cfg names the new (current) slaves, cleans out a couple of factories that are no longer needed (leopard, a duplicated osx, vista, xp) and also adds the call to a11y test for linux and mac.

Comment 1

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: Mozbuild.py patch

Comment 2

[[e-mail] (:bhearsum)]

Comment on attachment 344313 [details] [diff] [review]
Mozbuild.py patch

>--- repo_mozbuild_py	2008-10-22 12:47:06.000000000 -0400
>+++ current_use_mozbuild_py	2008-10-22 13:24:08.000000000 -0400

> MozillaEnvironments['mozbuild'] = {
>+MozillaEnvironments['mozbuild2'] = {
> MozillaEnvironments['mozbuild_pgo'] = {

I realize we're just doing an import, but I would like to know why we have three different environments for windows. Are the slaves not the same? I don't see why PGO should need a different env.

>+class MozillaWinXPMochitest(MozillaMochitest):
>+    command = ['perl runtests.pl --appname=..\\..\\..\\dist\\bin\\firefox.exe --autorun --console-level=INFO --close-when-done']
>+class MozillaWinXPMochichrome(MozillaMochichrome):
>+   command = ['perl runtests.pl --appname=..\\..\\..\\dist\\bin\\firefox.exe --chrome --autorun --console-level=INFO --close-when-done']
>+class MozillaWinXPBrowserChromeTest(MozillaBrowserChromeTest):
>+    command = ['perl runtests.pl --appname=../../../dist/bin/firefox.exe --autorun --browser-chrome --close-when-done']

As discussed on IRC, please remove the WinXP classes (if we need winxp machines again we should probably use runtests.py, anyways).

Comment 3

[[e-mail] (:bhearsum)]

Comment on attachment 344312 [details] [diff] [review]
[checked in] Master.cfg patch

I would really like to unify the win32 environments if there's no useful differences between them. I have a feeling that's not the case though....

Comment 4

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: [checked in] Mozbuild.py patch

No more win xp.

I wish we could unify the win32 environments, but the pgo is different than the two non-pgo - they are both DL360's and the pgo is a VM.  

Not sure if it's worth it to replace those with VMs when we are within 6 months of dropping this branch

Comment 5

[[e-mail] (:bhearsum)]

(In reply to comment #4)
> Created an attachment (id=344929) [details]
> Mozbuild.py patch
> 
> No more win xp.
> 
> I wish we could unify the win32 environments, but the pgo is different than the
> two non-pgo - they are both DL360's and the pgo is a VM.  
> 

Well, even with hardware it should be possible to setup hosts with the same PATHs :). If they aren't setup that way I'm not going to make you do it, though.

> Not sure if it's worth it to replace those with VMs when we are within 6 months
> of dropping this branch

It's working as it is, let's not screw with that.

Comment 6

[[e-mail] (:bhearsum)]

Actually, why is there still mozbuild and mozbuild2? Those slaves aren't the same either?

Comment 7

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 344929 [details] [diff] [review]
[checked in] Mozbuild.py patch

Checking in master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/testing/unittest/master.cfg,v  <--  master.cfg
new revision: 1.39; previous revision: 1.38
done
Checking in mozbuild.py;
/cvsroot/mozilla/tools/buildbot-configs/testing/unittest/mozbuild.py,v  <--  mozbuild.py
new revision: 1.25; previous revision: 1.24
done

Comment 8

[Lukas Blakk [:lsblakk] use ?needinfo]

Closing, the a11y tests are running on Production 1.9 now.