Closed Bug 637858 Opened 14 years ago Closed 14 years ago

Enable (some) reftests for out-of-process content on Fedora machines

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cjones, Assigned: armenzg)

Details

Spun off from bug 623613. To summarize, we want to run these tests with the pref browser.tabs.remote=true and MOZ_LAYERS_FORCE_SHMEM_SURFACES=1 in the environment. We'll get a large benefit from just enabling reftests for even one directory that currently passes all tests, so that we can tell when m-c pushes completely break out-of-process content.
Do you know the subset or not yet?
First candidate would be layout/reftests/reftest-sanity/reftest.list, but I need to check if they're still passing.
In the opt run in bug 623613, all the reftest-sanity tests passed.
In my last try push (263d877928ac) - all the linux reftest-ipcs passed layout/reftests/reftest-sanity/reftest.list - both the opt and debug builds failed another 30 or so tests - the debug builds also exhibited the leak that's showing up in debug crashtest-ipc So, I think we're ready to start running just layout/reftests/reftest-sanity/reftest.list on opt builds! Let me hunt down the runreftest.py incantation for that.
Looks like in the config we can just specify + elif suite in ('reftest-ipc'): + return ['--setpref=browser.tabs.remote=true', + 'reftest/tests/layout/reftests/reftest-sanity/reftest.list'] Instead of reftest/tests/layout/reftests/reftest.list.
The reftest-sanity tests are ready to be enabled. These will catch wholesale breakage of shadow-layers code, like what happened with the initial landing of bug 626602.
found in triage: can you clarify: 1) do you want us to run these tests with changed pref/env settings *and* also run the same test suites without changing pref/env settings? 2) This bug only mentions Fedora machines. how do you want us to handle testing on win32, osx, android, maemo?
This got fixed in bug 623613. With: https://bugzilla.mozilla.org/show_bug.cgi?id=623613#attachflag6 on March 2nd.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee: nobody → armenzg
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.