1160755 - Port |Bug 920223 - Mass convert MOCHITEST_* variables to manifests| to SeaMonkey - All mochitests fail on comm-central

Status: RESOLVED DUPLICATE of bug 773349

(SeaMonkey :: Build Config, defect)

Description

[Ian Neal]

When you try to run a mochitest against comm-central for example mochitest-browser-chrome against SeaMonkey it fails:
TEST_PATH=suite/browser/test/browser_bug561636.js make -C ../sm-opt/ mochitest-browser-chrome
make: Entering directory '/home/gizmo/central/sm-opt'
rm -f ./mochitest-browser-chrome.log && /home/gizmo/central/sm-opt/_virtualenv/bin/python _tests/testing/mochitest/runtests.py --autorun --close-when-done --console-level=INFO --log-tbpl=./mochitest-browser-chrome.log --failure-file=/home/gizmo/central/sm-opt/_tests/testing/mochitest/makefailures.json --testing-modules-dir=/home/gizmo/central/sm-opt/_tests/modules --extra-profile-file=dist/plugins --symbols-path=dist/crashreporter-symbols --test-path='suite/browser/test/browser_bug561636.js'  --browser-chrome
Checking for orphan ssltunnel processes...
Checking for orphan xpcshell processes...
SUITE-START | Running 0 tests
TEST-INFO | checking window state
Browser Chrome Test Summary
	Passed: 0
	Failed: 0
	Todo: 0
*** End BrowserChrome Test Results ***
SUITE-END | took 0s
/home/gizmo/central/comm-central/mozilla/../suite/build.mk:30: recipe for target 'mochitest-browser-chrome' failed
make: *** [mochitest-browser-chrome] Error 1
make: Leaving directory '/home/gizmo/central/sm-opt

Are there any recent changes to framework that could have caused this?

Comment 1

[Ian Neal]

Was definitely working 2015-04-07 13:07:51 PDT

Comment 2

[Ian Neal]

(In reply to Ian Neal from comment #1)
> Was definitely working 2015-04-07 13:07:51 PDT
Scratch that.

Having done further testing, last release that it definitely worked on was SM2.26 (Gecko 29). When I looked at SM2.29 (Gecko 32), there was an issue with not being able to import uses_marionette.
For SM2.30 (Gecko 33), I get a "No rule to make target 'mochitest-browser-chrome'. Stop."
For SM2.31 (Gecko 34) and SM2.32 (Gecko 35), it starts and then stops the MochitestServer but doesn't run any tests.
Maybe related to the ccrework which happened around that sort of time. cc'ing jcranmer for his view.

Comment 3

[Joshua Cranmer [:jcranmer]]

I plead complete ignorance on mochitest. Thunderbird has never used it, so I've never bothered to look at any of the details. I've generally inspected SeaMonkey's specific build files to make sure none of my changes directly affected them, but any testing I did was strictly limited to building SM and making sure the resulting project worked in a simple smoke test.

Comment 4

[Ian Neal]

So having done some digging, looks like we need to at least port changes to Makefile.in/moz.build files made in Bug 920223.
Was there a script used?

Comment 5

[Ian Neal]

Lots of catchup work it seems, duping to bug 773349 as that was where some of the work was initially identified.