Closed Bug 1448197 Opened 5 years ago Closed 3 years ago
Rewrite Marionette test for the Safe Mode policy
We should clean up this test addressing the comments made by Henrik on bug 1440573 comment 50.
Please note that this test also causes another set of perma failures for our new Windows workers on TaskCluster: https://firstname.lastname@example.org&selectedJob=169866847&filter-searchStr=marionette Here details from the log viewer: https://treeherder.mozilla.org/logviewer.html#?job_id=169866859&repo=try&lineNumber=1397-1402 > 14:11:52 ERROR - TEST-UNEXPECTED-ERROR | testing\marionette\harness\marionette_harness\tests\unit\test_cli_arguments.py TestCommandLineArguments.test_safe_mode_blocked_by_policy | WindowsError: [Error 5] Access is denied > 14:11:52 INFO - Traceback (most recent call last): > 14:11:52 INFO - File "Z:\task_1521814095\build\venv\lib\site-packages\marionette_harness\marionette_test\testcases.py", line 159, in run > 14:11:52 INFO - testMethod() > 14:11:52 INFO - File "Z:\task_1521814095\build\tests\marionette\tests\testing\marionette\harness\marionette_harness\tests\unit\test_cli_arguments.py", line 51, in test_safe_mode_blocked_by_policy > 14:11:52 INFO - reg_policies = winreg.OpenKeyEx(winreg.HKEY_CURRENT_USER, "SOFTWARE\\Policies", 0, winreg.KEY_WRITE) Pete, as you mentioned in the email we don't allow that yet, and it would need a fix for the Windows worker?
I'm on PTO this week, but ideally it is preferred if individual tests do not require system changes (such as custom ACLs to be enacted) in order to run. If they are necessary, we can apply them, but it adds to the complexity of system set-up. Many thanks!
Felipe, can you please add details so that we know if such privileges are necessary? Thanks.
Regarding the location of the test, it would be great if we can move it to a better place. Mn jobs are really for unit tests only, and we should not continue to clutter it even more. Would it be ok for you to move it to firefox-ui functional tests? We could add a new subfolder like "policy" under https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/functional/
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/5c8cbf2a5088 Backout Marionette policy test that should be rewritten. r=backout test-only
I backed out that test from mozilla-central (and didn't uplift it to beta), so that we can properly rewrite it.
Summary: Clean up Marionette test for Safe Mode → Rewrite Marionette test for the Safe Mode policy
Thanks a lot!
The leave-open keyword is there and there is no activity for 6 months. :Felipe, maybe it's time to close this bug?
The bug is still valid, so I'm just gonna remove the leave-open keyword. The cset that landed here was a backout, and the leave-open was added just to avoid this bug getting closed at the time.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.