Open Bug 1034624 Opened 7 years ago Updated 4 years ago
--debugger=gdb sets an incorrect working directory for chrome mochitests
STEPS TO REPRODUCE: mach mochitest-chrome --debugger=gdb toolkit/components/ctypes/tests/chrome/test_ctypes.xul and type "run" at the gdb prompt. EXPECTED RESULTS: Test passes. ACTUAL RESULTS: Test fails like so: TEST-UNEXPECTED-FAIL | chrome://mochitests/content/chrome/toolkit/components/ctypes/tests/chrome/test_ctypes.xul | Chrome test dir doesn't exist?! This is happening because when the test calls getCurrentDir(undefined) (location.path is undefined) it gets back something like: $objdir/chrome/toolkit/components/ctypes/tests/chrome whereas if I run without --debugger=gdb it gets back something like: $objdir/_tests/testing/mochitest/chrome/toolkit/components/ctypes/tests/chrome and while the latter exists, the former does not.
Summary: Some chrome mochitests are run differently depending on whether --debugger=gdb was passed → --debugger=gdb sets an incorrect working directory for chrome mochitests
Component: Mochitest Chrome → Mochitest
You need to log in before you can comment on or make changes to this bug.