Closed
Bug 1143218
Opened 9 years ago
Closed 9 years ago
Use mochitest subsuites to specify webgl tests
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(firefox36 fixed, firefox37 fixed, firefox38 fixed, firefox39 fixed)
People
(Reporter: jgilbert, Assigned: jgilbert)
References
Details
Attachments
(2 files, 5 obsolete files)
7.00 KB,
patch
|
jmaher
:
review+
gbrown
:
review+
|
Details | Diff | Splinter Review |
7.65 KB,
patch
|
gbrown
:
review+
|
Details | Diff | Splinter Review |
We already have a "mochitest-subsuite-webgl.ini" file. We should hook it up to the subsuite system and use that to specify tests for mochitest-gl(s).
Attachment #8577510 -
Flags: review?(jmaher)
Assignee | ||
Comment 1•9 years ago
|
||
I took a stab at this, but I'm not sure I know what I'm doing when in mozharness. :)
Assignee: nobody → jgilbert
Attachment #8577517 -
Flags: review?(jmaher)
Comment 2•9 years ago
|
||
Comment on attachment 8577510 [details] [diff] [review] 0001-Mark-mochetest-subsuite-webgl-as-subsuite-webgl.patch Review of attachment 8577510 [details] [diff] [review]: ----------------------------------------------------------------- our problem comes with https://dxr.mozilla.org/mozilla-central/source/dom/canvas/test/_webgl-conformance.ini, is there a way we could put the subsuite = webgl in there as well?
Attachment #8577510 -
Flags: review?(jmaher) → review-
Comment 3•9 years ago
|
||
Comment on attachment 8577517 [details] [diff] [review] mozharness-subsuite-gl.diff Review of attachment 8577517 [details] [diff] [review]: ----------------------------------------------------------------- These are the right changes! I think we have a couple of extra files to consider changing in m-c: testing/config/mozharness/android_arm_config.py testing/config/mozharness/android_arm_4_3_config.py :gbrown, do you see anything else we should change as well?
Attachment #8577517 -
Flags: review?(jmaher)
Attachment #8577517 -
Flags: review?(gbrown)
Attachment #8577517 -
Flags: review+
Assignee | ||
Comment 4•9 years ago
|
||
(In reply to Joel Maher (:jmaher) from comment #2) > Comment on attachment 8577510 [details] [diff] [review] > 0001-Mark-mochetest-subsuite-webgl-as-subsuite-webgl.patch > > Review of attachment 8577510 [details] [diff] [review]: > ----------------------------------------------------------------- > > our problem comes with > https://dxr.mozilla.org/mozilla-central/source/dom/canvas/test/_webgl- > conformance.ini, is there a way we could put the subsuite = webgl in there > as well? Yep, I can make this happen.
Flags: needinfo?(jgilbert)
Comment 5•9 years ago
|
||
Comment on attachment 8577517 [details] [diff] [review] mozharness-subsuite-gl.diff Review of attachment 8577517 [details] [diff] [review]: ----------------------------------------------------------------- I agree that android_arm_config.py (Android 2.3) and android_arm_4_3_config.py (new Android 4.3 platform coming soon) should also be included.
Attachment #8577517 -
Flags: review?(gbrown) → review+
Assignee | ||
Comment 6•9 years ago
|
||
Attachment #8577510 -
Attachment is obsolete: true
Flags: needinfo?(jgilbert)
Attachment #8578261 -
Flags: review?(jmaher)
Comment 7•9 years ago
|
||
Comment on attachment 8578261 [details] [diff] [review] 0001-Mark-mochetest-subsuite-webgl-as-subsuite-webgl.patch Review of attachment 8578261 [details] [diff] [review]: ----------------------------------------------------------------- this looks great- now to get this landed :) First thing to do is to test this on try. You can create a custom mozharness repo with your mozharness patch: http://armenzg.blogspot.com/2014/12/test-mozharness-changes-on-try.html then adjust testing/mozharness/mozharness.json to point to your repo, and then these changes into the patch queue and push to try. Make sure to test android and desktop!
Attachment #8578261 -
Flags: review?(jmaher) → review+
Assignee | ||
Comment 8•9 years ago
|
||
Attachment #8578270 -
Flags: review?(jmaher)
Assignee | ||
Comment 9•9 years ago
|
||
Attachment #8578271 -
Flags: review?(jmaher)
Comment 10•9 years ago
|
||
Comment on attachment 8578270 [details] [diff] [review] 0002-Use-subsuite-webgl.patch Review of attachment 8578270 [details] [diff] [review]: ----------------------------------------------------------------- great stuff here!
Attachment #8578270 -
Flags: review?(jmaher) → review+
Comment 11•9 years ago
|
||
Comment on attachment 8578271 [details] [diff] [review] 0003-Remove-now-unused-gl.json.patch Review of attachment 8578271 [details] [diff] [review]: ----------------------------------------------------------------- I don't see gl.json in the tree, nor a reference to it in moz.build. Is your tree out of date?
Attachment #8578271 -
Flags: review?(jmaher) → review+
Assignee | ||
Comment 12•9 years ago
|
||
r=jmaher And yes, I was on trunk from a number of days ago. Patch 3 here is already in the tree in some form.
Attachment #8578270 -
Attachment is obsolete: true
Attachment #8578271 -
Attachment is obsolete: true
Attachment #8578335 -
Flags: review+
Comment 13•9 years ago
|
||
are we ready to land? we are uplifting to aurora/beta and run into these issues.
Assignee | ||
Comment 14•9 years ago
|
||
This should have the pinning right: https://treeherder.mozilla.org/#/jobs?repo=try&revision=85c10a98f19b
Comment 15•9 years ago
|
||
ok, one thing we overlooked: https://dxr.mozilla.org/mozilla-central/source/testing/mochitest/runtests.py#585 --subsuite is assumed to be browser-chrome. A couple of ideas here: 1) require --subsuite=devtools, to have --browser-chrome as well 2) special case --subsuite=devtools to be browser chrome and the rest to be plain I am sure there is something else we could do.
Flags: needinfo?(ted)
Flags: needinfo?(ahalberstadt)
Comment 16•9 years ago
|
||
I don't understand why --subsuite needs to be browser-chrome, that just seems.. wrong. Can we fix runtests.py so --subsuite can be applied to any flavor?
Flags: needinfo?(ahalberstadt)
Comment 17•9 years ago
|
||
we can fix it, I wanted to know what the preferred way to fix it would be? I just looked at the devtools stuff and they still specify --browser-chrome. this might be an easy fix.
Comment 18•9 years ago
|
||
when try opens, I will push to try with additional changes to support subsuite.
Flags: needinfo?(ted)
Comment 19•9 years ago
|
||
Yeah, so it might just be a matter of removing options.subsuite from here: https://dxr.mozilla.org/mozilla-central/source/testing/mochitest/runtests.py#585
Comment 20•9 years ago
|
||
on try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=6be883ad210d
Comment 21•9 years ago
|
||
this patch has the runtests.py changes, but it also has the changes for mozharness to point to the custom user repo. We would need to land the mozharness changes, then take this patch and update mozharness.json to point to the new revision. The try run looks good including looking at 8-10 raw logs and verifying we ran the right tests in the right jobs.
Attachment #8578261 -
Attachment is obsolete: true
Attachment #8578335 -
Attachment is obsolete: true
Attachment #8580584 -
Flags: review?(gbrown)
Comment 22•9 years ago
|
||
(In reply to Joel Maher (:jmaher) from comment #15) > A couple of ideas here: > 1) require --subsuite=devtools, to have --browser-chrome as well > 2) special case --subsuite=devtools to be browser chrome and the rest to be > plain Either of these seem fine, I'm not sure why this is like this.
Comment 23•9 years ago
|
||
Comment on attachment 8580584 [details] [diff] [review] cumulative patch with runtests fixed (1.0) Review of attachment 8580584 [details] [diff] [review]: ----------------------------------------------------------------- I agree the try run looks good. Good stuff here! Since this is loosely related, would you mind setting the mochitest-gl total-chunks in android_arm_4_3_config.py to 4? This was updated recently for 2.3 and the 4.3 config update was missed.
Attachment #8580584 -
Flags: review?(gbrown) → review+
Comment 24•9 years ago
|
||
mozharness changes on default: http://hg.mozilla.org/build/mozharness/rev/b7285d1f1272
Comment 25•9 years ago
|
||
(In reply to Joel Maher (:jmaher) from comment #24) > mozharness changes on default: > http://hg.mozilla.org/build/mozharness/rev/b7285d1f1272 cherry-picked to production: https://hg.mozilla.org/build/mozharness/rev/7b5d3fcc48c6
Comment 26•9 years ago
|
||
inbound: https://hg.mozilla.org/integration/mozilla-inbound/rev/e3be61bda115
Comment 28•9 years ago
|
||
we probably need to uplift this to aurora/beta- RyanVM, where do we need this?
Flags: needinfo?(ryanvm)
Comment 29•9 years ago
|
||
I actually just kicked off Try pushes for this rebased on to Aurora, Beta, and Release. https://treeherder.mozilla.org/#/jobs?repo=try&revision=bdfe1112a65c https://treeherder.mozilla.org/#/jobs?repo=try&revision=a58b8b594396 https://treeherder.mozilla.org/#/jobs?repo=try&revision=58fe203296af
Flags: needinfo?(ryanvm)
Comment 31•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/0db9fff35382 https://hg.mozilla.org/mozilla-central/rev/95ec024d2e6b
Comment 32•9 years ago
|
||
(In reply to Carsten Book [:Tomcat] from comment #31) > https://hg.mozilla.org/mozilla-central/rev/0db9fff35382 > https://hg.mozilla.org/mozilla-central/rev/95ec024d2e6b These were from bug 1142318 in case anybody comes here looking for them.
Comment 33•9 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/bdfe1112a65c https://hg.mozilla.org/releases/mozilla-beta/rev/a58b8b594396 https://hg.mozilla.org/releases/mozilla-release/rev/58fe203296af And of course, this changed the chunking around enough on Windows to cause bug 1146061. *sigh*
Comment 34•9 years ago
|
||
mozharness production tag moved to: https://hg.mozilla.org/build/mozharness/rev/production
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•