Open Bug 612796 Opened 9 years ago Updated 9 years ago
.9 .1 regression: Chrome file doesn't exist: $OBJDIR/_tests/reftest/reftest/chrome/reftest/content/autoconf .js
I can no longer run crashtests locally in my 1.9.1 tree. STEPS TO REPRODUCE 0. build (1.9.1 branch) Firefox DEBUG build from scratch 1. python $OBJDIR/_tests/reftest/runreftest.py testing/crashtest/crashtests.list ACTUAL RESULTS Chrome file doesn't exist: $OBJDIR/_tests/reftest/reftest/chrome/reftest/content/autoconf.js REFTEST TEST-UNEXPECTED-FAIL | | EXCEPTION: ReferenceError: gAutoconfVars is not defined REFTEST FINISHED: Slowest test took 0ms (undefined) REFTEST INFO | Result summary: REFTEST INFO | Successful: 0 (0 pass, 0 load only) REFTEST INFO | Unexpected: 1 (0 unexpected fail, 0 unexpected pass, 0 failed load, 1 exception) REFTEST INFO | Known problems: 0 (0 known fail, 0 random, 0 skipped) REFTEST INFO | Total canvas count = 0 REFTEST INFO | Quitting...
Ftr, m-1.9.1 'Linux opt' tinderbox is green, but tests are not run on Linux64 or Debug. (In reply to comment #0) > Chrome file doesn't exist: > $OBJDIR/_tests/reftest/reftest/chrome/reftest/content/autoconf.js I'm not familiar with this 1st error, iirc. See: http://mxr.mozilla.org/mozilla1.9.1/search?string=autoconf.js&case=1&find=%2Flayout%2Ftools%2Freftest%2F > REFTEST TEST-UNEXPECTED-FAIL | | EXCEPTION: ReferenceError: gAutoconfVars is > not defined Odd, this 2nd error was supposed to be fixed by bug 492228: I assume it's caused by the first error. > REFTEST FINISHED: Slowest test took 0ms (undefined) (I never like "undefined"...)
tar: reftest/chrome/reftest/content/autoconf.js: Cannot stat: Too many levels of symbolic links
You need to log in before you can comment on or make changes to this bug.