Closed Bug 982225 Opened 12 years ago Closed 12 years ago

Run additional hidden 3 debug mochitest-browser-chrome chunks and b2g reftests

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: armenzg)

References

Details

Attachments

(8 files, 2 obsolete files)

1.32 KB, patch
rail
: review+
armenzg
: checked-in+
Details | Diff | Splinter Review
797 bytes, patch
jmaher
: review+
armenzg
: checked-in+
Details | Diff | Splinter Review
1.07 KB, patch
armenzg
: review+
philor
: checked-in+
Details | Diff | Splinter Review
4.44 KB, patch
rail
: review+
armenzg
: checked-in+
Details | Diff | Splinter Review
1.18 KB, patch
mozilla
: review+
armenzg
: checked-in+
Details | Diff | Splinter Review
1.36 KB, patch
rail
: review+
armenzg
: checked-in+
Details | Diff | Splinter Review
1.64 KB, patch
rail
: review+
Details | Diff | Splinter Review
9.50 KB, text/plain
Details
No description provided.
Given that we know absolutely for sure that 3-chunk behaves differently than 1-chunk, "on m-i and then other branches" needs to be "and then a few hours later" not even "a few days later."
we have tested 3 chunk on cedar, changing this delicate balance will cause fires to burn, earthquakes to strike and RyanVM to lose the brown in his hair. We need to move to ec2 machines instead of hardware for linux bc tests, and on debug the only realistic way to do that is via chunking.
I'm told that the actual plan is to run 3-chunk hidden on m-i while still running 1-chunk visible, and then once 3-chunk shows it's stable and green, switch over to 3-chunk on all trunk trees, which is a fine and sensible plan.
Summary: Switch to 3 debug mochitest-browser-chrome chunk for m-i and then other branches → Run additional hidden 3 debug mochitest-browser-chrome chunks on m-i, and then switch on all trunk branches
Blocks: 837017
Attachment #8389378 - Flags: review?(rail) → review+
hey there, I'm not sure if this is it but I think our test masters will fail if we merge to default. I see this land: http://hg.mozilla.org/build/buildbot-configs/rev/4da229fa0b07 but this differs from https://bugzilla.mozilla.org/attachment.cgi?id=8389378&action=edit in that it adds 'linux-debug'. checkconfig complains about that key. Jenkiins should have caught this but it got up and quit on march 6th... :( Disclaimer: I am probably wrong about something here :)
I backed it out: http://hg.mozilla.org/build/buildbot-configs/rev/4da229fa0b07 checkconfig works again. apologies if I was wrong in doing so.
Attachment #8389378 - Flags: checked-in+
in production
Blocks: 981775
bc2 & bc3 are looking green on m-i. bc2 sometimes goes red when it goes over 4200 seconds (successful runs go around 4000 seconds).
Attachment #8390659 - Flags: review?(jmaher)
Comment on attachment 8390659 [details] [diff] [review] bump bc2 10 more minutes Review of attachment 8390659 [details] [diff] [review]: ----------------------------------------------------------------- this looks great.
Attachment #8390659 - Flags: review?(jmaher) → review+
Attachment #8390659 - Flags: checked-in+
Live.
4800 wasn't enough, we still exceed it. 6000 has the amusing property of being half of what I increased the unchunked maxtime to, since bc2 is really (along with parts of bc3) devtools-chrome, and that's where the slow is.
Attachment #8392452 - Flags: review?(armenzg)
Comment on attachment 8392452 [details] [diff] [review] and another 20 minutes Review of attachment 8392452 [details] [diff] [review]: ----------------------------------------------------------------- Thank you philor.
Attachment #8392452 - Flags: review?(armenzg) → review+
Live in production.
Attached file builders being added by previous patch (obsolete) —
Attachment #8395918 - Flags: feedback?(rail)
Comment on attachment 8395917 [details] [diff] [review] run 3 chunks for debug mochitest-browser-chrome on EC2 machines (side-by-side with Fedora 1-chunk) on up to Gecko30 branches Review of attachment 8395917 [details] [diff] [review]: ----------------------------------------------------------------- ::: mozilla-tests/config.py @@ +1992,5 @@ > > +# Enable debug mochitest-browser-chrome on EC2 > +# For branches newer than Gecko 30 (including) > +for name, branch in items_at_least(BRANCHES, 'gecko_version', 30): > + if branch['platforms'].has_key('linux'): A nit. Can you use the following instead of has_key (PEP8 suggest to avoid using has_key): if 'linux' in branch['platforms']: .... @@ +1994,5 @@ > +# For branches newer than Gecko 30 (including) > +for name, branch in items_at_least(BRANCHES, 'gecko_version', 30): > + if branch['platforms'].has_key('linux'): > + branch['platforms']['linux']['ubuntu32_vm']['debug_unittest_suites'] += MOCHITEST_BC_3[:] > + if branch['platforms'].has_key('linux'): the same here.
Attachment #8395917 - Flags: review?(rail) → review+
Attachment #8395918 - Flags: feedback?(rail) → feedback+
Comment on attachment 8395917 [details] [diff] [review] run 3 chunks for debug mochitest-browser-chrome on EC2 machines (side-by-side with Fedora 1-chunk) on up to Gecko30 branches https://hg.mozilla.org/build/buildbot-configs/rev/8fc0876e3c1c
Attachment #8395917 - Flags: checked-in+
No longer blocks: 837017
Blocks: 864866
Summary: Run additional hidden 3 debug mochitest-browser-chrome chunks on m-i, and then switch on all trunk branches → Run additional hidden 3 debug mochitest-browser-chrome chunks and b2g reftests
something is in production
Depends on: 988147
I want to see on what state we're on those branches.
Attachment #8397400 - Flags: review?(aki)
Attachment #8397400 - Flags: review?(aki) → review+
Attachment #8397400 - Flags: checked-in+
in production
Hidden on b2g28 and b2g26 until they're greened up.
Attachment #8395918 - Attachment is obsolete: true
Comment on attachment 8401447 [details] [diff] [review] Enable debug mochitest-browser chrome for Ubuntu {x64} for the release branches Wooooo!
Attachment #8401447 - Flags: review?(rail) → review+
Comment on attachment 8401447 [details] [diff] [review] Enable debug mochitest-browser chrome for Ubuntu {x64} for the release branches http://hg.mozilla.org/build/buildbot-configs/rev/575ccb9b4185
Attachment #8401447 - Flags: checked-in+
Live in production.
We need to wait until one last uplift happens and some good communications, however, it is not bad to have the patch reviewed already. Once we're completely done with the minis, a clean up patch will be required to remove the platform completely.
Attachment #8398469 - Attachment is obsolete: true
Attachment #8402669 - Flags: review?(rail)
Attachment #8402669 - Flags: review?(rail) → review+
I'm going crazy with so many bugs. I will do any follow up patches in bug 864866 (the tracking bug).
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: