Closed
Bug 628384
Opened 14 years ago
Closed 14 years ago
Bypass graphics blacklist on reftest and mochitest
Categories
(Testing :: Reftest, defect)
Testing
Reftest
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bjacob, Assigned: bjacob)
References
Details
Attachments
(2 files, 1 obsolete file)
1.54 KB,
patch
|
dbaron
:
review+
|
Details | Diff | Splinter Review |
2.07 KB,
patch
|
ehsan.akhgari
:
review-
|
Details | Diff | Splinter Review |
This is a cousing of bug 628377, refer to it for context.
This patch bypasses the graphics blacklist in reftests.
Attachment #506511 -
Flags: review?(jmaher)
Comment on attachment 506511 [details] [diff] [review]
force-enable gfx features in reftests
Please don't do it this way; see bug 608030, which I'll hopefully land in an hour or two.
Attachment #506511 -
Flags: review?(jmaher) → review-
(In particular, runreftest.py should be a helpful script, and not required; prefs that are important for correct testing should be set in the harness, as the patch there does.)
Assignee | ||
Comment 4•14 years ago
|
||
Like this?
(can't be sure as there were multiple patches in the bug you mentioned)
Attachment #506511 -
Attachment is obsolete: true
Attachment #506870 -
Flags: review?(dbaron)
Comment on attachment 506870 [details] [diff] [review]
force-enable gfx features in reftests, updated
This is ok, but it applies it to both reftest and mochitest and some other test suites.
If you only need reftest, it might be better to do only reftest, which would mean patching the pref-setting code in http://hg.mozilla.org/mozilla-central/file/6a097e294828/layout/tools/reftest/reftest-cmdline.js#l95
Comment on attachment 506870 [details] [diff] [review]
force-enable gfx features in reftests, updated
marking review- to prompt response to previous comment, in case you missed it
Attachment #506870 -
Flags: review?(dbaron) → review-
Assignee | ||
Comment 7•14 years ago
|
||
Thanks, I had actually missed it :-)
I need this to apply to all tests that run on test slaves, so the fact that it applies to mochitests, if unintentional, is very welcome. So far there is only one mochitest that should be affected, the WebGL mochitest, and I was addressing this directly in it.
Given that it's a good thing that this applies to all tests, i set this back to r?.
Assignee | ||
Updated•14 years ago
|
Attachment #506870 -
Flags: review- → review?(dbaron)
Comment on attachment 506870 [details] [diff] [review]
force-enable gfx features in reftests, updated
r=dbaron
Attachment #506870 -
Flags: review?(dbaron) → review+
Summary: Bypass graphics blacklist on Reftest → Bypass graphics blacklist on reftest and mochitest
Assignee | ||
Comment 9•14 years ago
|
||
Since drivers were upgraded today on test slaves, this is no longer needed.
Thanks for your help and sorry for the noise! I couldn't know how long it would
take to update the drivers on test slaves.
I guess that INVALID is the most appropriate bug resolution...
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Assignee | ||
Comment 10•14 years ago
|
||
Reopening! Indeed, only the Win7 test slaves have up-to-date drivers, the WinXP slaves don't. So I really need to land this patch.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment on attachment 506870 [details] [diff] [review]
force-enable gfx features in reftests, updated
a2.0=dbaron
Assignee | ||
Comment 12•14 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 13•14 years ago
|
||
oops! should only have applied that to win32.
Attachment #507988 -
Flags: review?(dbaron)
Attachment #507988 -
Flags: review?(dbaron) → review+
Comment 14•14 years ago
|
||
Comment on attachment 507988 [details] [diff] [review]
only apply to win32
r- because this also affects locally run tests.
This sounds to me like something that we'd want to fix on the test slaves, not on the machines of every developer working on the project.
Attachment #507988 -
Flags: review+ → review-
Updated•14 years ago
|
Assignee: nobody → bjacob
You need to log in
before you can comment on or make changes to this bug.
Description
•