Open Bug 989855 Opened 11 years ago Updated 3 years ago

mach mochitest-plain doesn't understand symlinks

Categories

(Testing :: Mochitest, defect)

x86_64
Linux
defect

Tracking

(Not tracked)

People

(Reporter: karlt, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

+++ This bug was initially created as a clone of Bug #911646 +++ % ./mach mochitest-plain content/media/webaudio/test AssertionError File "/home/karl/moz/dev/testing/mochitest/mach_commands.py", line 578, in run_mochitest_plain return self.run_mochitest(test_paths, 'plain', **kwargs) File "/home/karl/moz/dev/testing/mochitest/mach_commands.py", line 633, in run_mochitest test_paths=test_paths, suite=flavor, **kwargs) File "/home/karl/moz/dev/testing/mochitest/mach_commands.py", line 370, in run_desktop_test result = runner.runTests(options) File "/home/karl/moz/dev/obj/_tests/testing/mochitest/runtests.py", line 1111, in runTests testURL = self.buildTestPath(options) File "/home/karl/moz/dev/obj/_tests/testing/mochitest/runtests.py", line 471, in buildTestPath assert pathAbs.startswith(testRootAbs)
TEST_PATH=content/media/webaudio/test make -C obj/ mochitest-plain behaves as expected.
Severity: blocker → normal
Where's the symlink in this setup?
% ls -l obj lrwxrwxrwx 1 karl users 19 Jun 29 2013 obj -> /mnt/sda11/karl/obj % grep obj .mozconfig mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj
I think you'll be much happier if you teach your mozconfig about the real path and use the symlink only for convenience. There is path resolution code everywhere in the tree. Sadly, you can't count on symlinks "just working" everywhere, as convenient as that would be. (You don't have to remind me this is a regression.) I apologize for the inconvenience.
Component: Build Config → Mochitest
Product: Core → Testing
(In reply to Gregory Szorc [:gps] from comment #4) > I think you'll be much happier if you teach your mozconfig about the real > path and use the symlink only for convenience. That seems to work, thanks.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.