Closed Bug 1342202 Opened 7 years ago Closed 7 years ago

Move Win7 mochitest-a11y to AWS

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RyanVM, Assigned: spacurar)

References

Details

Attachments

(3 files, 7 obsolete files)

Component: General Automation → Buildduty
QA Contact: catlee → bugspam.Callek
Assignee: nobody → spacurar
Attached patch bug_1342202.patch (obsolete) — Splinter Review
Attachment #8841963 - Flags: review?(kmoir)
Attached file diff (obsolete) —
So I notice that in the diff that there are three or two jobs removed, but six or four jobs added.  Is this expected?  Shouldn't the jobs just be replaced on a one for one basis?

< Windows 7 32-bit autoland opt test mochitest-a11y ScriptFactory
< Windows 7 32-bit autoland pgo test mochitest-a11y ScriptFactory
1233d1230
< Windows 7 32-bit autoland debug test mochitest-a11y ScriptFactory
1373a1371,1372
> Windows 7 VM 32-bit autoland opt test mochitest-a11y ScriptFactory
> Windows 7 VM 32-bit autoland pgo test mochitest-a11y ScriptFactory
1449a1449
> Windows 7 VM 32-bit autoland debug test mochitest-a11y ScriptFactory
1475a1476,1477
> Windows 7 VM-GFX 32-bit autoland opt test mochitest-a11y ScriptFactory
> Windows 7 VM-GFX 32-bit autoland pgo test mochitest-a11y ScriptFactory
1492a1495
> Windows 7 VM-GFX 32-bit autoland debug test mochitest-a11y ScriptFactory
3113d3115
< Windows 7 32-bit elm opt test mochitest-a11y ScriptFactory
3122d3123
< Windows 7 32-bit elm debug test mochitest-a11y ScriptFactory
3196a3198
> Windows 7 VM 32-bit elm opt test mochitest-a11y ScriptFactory
3272a3275
> Windows 7 VM 32-bit elm debug test mochitest-a11y ScriptFactory
3285a3289
> Windows 7 VM-GFX 32-bit elm opt test mochitest-a11y ScriptFactory
3302a3307
> Windows 7 VM-GFX 32-bit elm debug test mochitest-a11y ScriptFactory
3801,3802d3805
I don't think we want the VM-GFX jobs.
Attached patch bug_1342202_v2.patch (obsolete) — Splinter Review
Attachment #8841991 - Flags: review?(kmoir)
Attached file diff_v2 (obsolete) —
Attachment #8841964 - Attachment is obsolete: true
Attachment #8841963 - Attachment is obsolete: true
Attachment #8841963 - Flags: review?(kmoir)
Comment on attachment 8841991 [details] [diff] [review]
bug_1342202_v2.patch

lgtm! thanks!
Attachment #8841991 - Flags: review?(kmoir) → review+
Attached patch bug_1342202_v3.patch (obsolete) — Splinter Review
We noticed travis errors after landing the patch and it turned out there were duplicates try tests for mochtest-a11y. Updated the patch to ignore try and checked that test-masters.sh returned no errors.
Attachment #8841991 - Attachment is obsolete: true
Attachment #8842370 - Flags: review?(aselagea)
Attached file diff_v3 (obsolete) —
Attachment #8841992 - Attachment is obsolete: true
Comment on attachment 8842370 [details] [diff] [review]
bug_1342202_v3.patch

lgtm
Attachment #8842370 - Flags: review?(aselagea) → review+
Attached patch bug_1342202_v4.patch (obsolete) — Splinter Review
Attachment #8842370 - Attachment is obsolete: true
Attachment #8842923 - Flags: review?(kmoir)
Attached file diff_v4
Attachment #8842371 - Attachment is obsolete: true
Comment on attachment 8842923 [details] [diff] [review]
bug_1342202_v4.patch

Instead of explicitly specifying the branch i.e. try, could you just check if mochitest-ally exists already in the list of test suites for the hardware platform, and delete it on the vm platform? For all the branches, not just try.
Sebastian, I don't know if you saw my comment on the bug earlier about refactoring, this is why I didn't review
Flags: needinfo?(spacurar)
I saw your comment and I'm currently working on it.
Flags: needinfo?(spacurar)
okay great :-) thank you very much
If it's taking too long to refactor don't worry about it and we can land it in it's present form.  Buildbot is on its way out anyways.
Comment on attachment 8842923 [details] [diff] [review]
bug_1342202_v4.patch

let's just land as is since buildbot is going away anyways
Attachment #8842923 - Flags: review?(kmoir) → review+
Sebastian, I reverted your patch because the tests failed.

https://travis-ci.org/mozilla-releng/build-buildbot-configs/builds/208623927
Attachment #8842923 - Attachment is obsolete: true
Attachment #8844826 - Flags: review?(kmoir)
Attached file diff_v5
This is the diff compared to the diff file from the patch in production (bug_1342202_v3). On the v3 patch mochitest-a11y wasn't disabled on win 7 ix on try branch.
Comment on attachment 8844826 [details] [diff] [review]
bug_1342202_v5.patch

Why is the diff only for try now (I thought it was needed for other branches).  Also, running test-master.sh show green results?
It is the diff compared to the v3 patch. For instance if I revert to the revision before Alin landed the patch, the differences would look just like the diffs from version 3 patch plus those 2 lines about win 32 ix on try branches being disabled. Yes, test-master.sh showed only green OK's.
Attachment #8844826 - Flags: review?(kmoir) → review+
Attachment #8844826 - Flags: checked-in+
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: