in trying to move tests to mochitest-chrome as part of the specialpowers test cleanup, I found that test_splitter.xul fails on winxp with 84 failures. I have a try server log file posted on my people account: http://people.mozilla.org/~jmaher/specialpowers/ Here is a sample of the failures: 9509 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft width moving -1,-1,,,-1 - got 1, expected 21 9510 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft height moving -1,-1 - got 26, expected 46 9511 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft width moving -1,0,,,-1 - got 1, expected 21 9513 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft width moving -1,1,,,-1 - got 1, expected 21 9514 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft height moving -1,1 - got 26, expected 6 9516 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft height moving 0,-1 - got 26, expected 46 9520 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft height moving 0,1 - got 26, expected 6 9521 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft width moving 1,-1,,,-1 - got 1, expected -19 9522 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft height moving 1,-1 - got 26, expected 46 9523 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft width moving 1,0,,,-1 - got 1, expected -19 9525 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft width moving 1,1,,,-1 - got 1, expected -19 9526 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/layout/xul/base/test/test_splitter.xul | resize element anchored-panel screen topleft height moving 1,1 - got 26, expected 6 if this shouldn't be in mochitest-chrome, please let me know, otherwise some help in getting this green on all platforms would be appreciated

There is no reason why this test couldn't be a chrome test. I can't think of any reason why this would fail on WinXP as a mochitest-chrome test. Have you tried to debug it?

I haven't spent a lot of time debugging it. After looking at it for 15-20 minutes, I moved on to work on the rest of the migration work. This is almost back on my radar, but if you have some good suggestions I am all ears!

test_splitter.xul is not using enablePrivilege. (anymore?)

we don't run tests on winxp on trunk(53+) so I am not sure if we can close this bug or actually finish the work started.

Why did we consider porting this test in the first place? Because it was XUL?

I believe so, that was 5.5 years ago.

It would be nice if we can disable remote XUL in mochitest-plain. The test environment would be more close to the actual environment.

is remote XUL a preference, or specific test cases?

It is controlled by the "allowXULXBL" permission. Test runner will blanket enable the permission. Each test file can use SpecialPowers.pushPermissions to override the permission.

Do we have a list of tests which need remote XUL? possibly starting there would determine what is left- maybe porting those tests to chrome or evaluating them for usefulness would be good next steps.

We have no such a list AFAIK.

I kicked a try run to estimate required changes: https://treeherder.mozilla.org/#/jobs?repo=try&revision=c1d2818a54eda70989607082fa90ecd5e31667cf&selectedJob=68014585

Made up from the test result. Interestingly, mochitest-chrome also has failures. Maybe because of bug 451630? I think we can close this bug for now because we have no benefit of porting.

(In reply to Masatoshi Kimura [:emk] from comment #13) > Created attachment 8826044 [details] > mochitest-failures.txt This list does not contain test_splitter.xul because the test crashes before it reaches to test_splitter.xul.