Closed Bug 976520 Opened 7 years ago Closed 7 years ago
_browser Element _inproc _Error Security .html seem to be permanently failing when switching to mochitest .ini manifests
as part of our big push to reduce complexity and add full support for a single manifest, we are moving entries from b2g.json -> mochitest.ini files. This is going well except for two tests: test_browserElement_[NoAttr|NoWhitelist].html These tests have been failing in bug 970290 intermittently, now they appear to be permanent.
I r+'d a patch yesterday that converts the dom/browser-element/ tests to mochitest.ini, if it is landing today, I would rather edit that, otherwise I will edit the .json file.
I will soon land patches for bug 970290 that make these two tests pass.
oh, looking forward to those, I will retest on try once you have those landed.
now that those two tests are passing, we have test_browserElement_inproc_ErrorSecurity.html failing: https://tbpl.mozilla.org/?tree=Try&rev=5dab0a650aa6 only on emulator opt though!
odd, this test is disabled according to the mochitest.ini file: http://dxr.mozilla.org/mozilla-central/source/dom/browser-element/mochitest/mochitest.ini#176 but in the mochitest-oop.ini, it is enabled: http://dxr.mozilla.org/mozilla-central/source/dom/browser-element/mochitest/mochitest-oop.ini#11 that mochitest-oop.ini doesn't have the proper support files, but we seem to be executing the support file. this is really odd because the patch we are testing doesn't change any b2g.json or mochitest.ini file for browser-element tests. jlebar, you wrote this test originally, any thoughts why it might be causing troubles for us?
Summary: test_browserElement_[NoAttr|NoWhitelist].html seem to be permanently failing when switching to mochitest.ini manifests → test_browserElement_inproc_ErrorSecurity.html seem to be permanently failing when switching to mochitest.ini manifests
It looks like Vivien originally disabled this test and added it to the list that wound up in mochitest-oop: http://hg.mozilla.org/mozilla-central/rev/ec2f1b9a9726 (Don't get too hung up on the manifests, I did my best to translate from the Makefiles to manifests, but there may have been something lost in translation.)
so should we be disabling this?
this test was originally disabled in b2g.json, it is an error in the patch we are testing. So since it was originally disabled, we can mark it as such in the appropriate patch and move on in life.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.