Closed Bug 1033449 Opened 10 years ago Closed 10 years ago

Gaia unit tests are perma-failing on b2g30_v1_4 since bug 874510 was merged into production

Categories

(Firefox OS Graveyard :: Gaia::TestAgent, defect)

x86_64
Linux
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RyanVM, Unassigned)

References

Details

b2g30 is closed until this is resolved.

https://tbpl.mozilla.org/php/getParsedLog.php?id=42950417&tree=Mozilla-B2g30-v1.4

b2g_ubuntu64_vm mozilla-b2g30_v1_4 opt test gaia-unit on 2014-07-02 09:04:13 PDT for push d597b94be592
slave: tst-linux64-spot-809

09:13:31     INFO -  gaia-unit-tests TEST-START | keyboard/test/unit/jspinyin_test.js |
09:13:31     INFO -  gaia-unit-tests TEST-START | keyboard/test/unit/jspinyin_test.js | jspinyin
09:13:31     INFO -  gaia-unit-tests TEST-UNEXPECTED-FAIL | keyboard/test/unit/jspinyin_test.js | jspinyin load | expected #{this} to equal #{exp}
09:13:31     INFO -  gaia-unit-tests INFO       | stack trace:
09:13:31     INFO -      Error: expected #{this} to equal #{exp}
09:13:31     INFO -          at chaiAssert (http://keyboard.gaiamobile.org:8080/common/test/helper.js:33:1)
09:13:31     INFO -          at assertEqual (http://keyboard.gaiamobile.org:8080/common/vendor/chai/chai.js:648:1)
09:13:31     INFO -          at (anonymous) (http://keyboard.gaiamobile.org:8080/common/vendor/chai/chai.js:2724:1)
09:13:31     INFO -          at isDefined (http://keyboard.gaiamobile.org:8080/common/vendor/chai/chai.js:1843:9)
09:13:31     INFO -          at (anonymous) (http://keyboard.gaiamobile.org:8080/test/unit/jspinyin_test.js:156:5)
09:13:31     INFO -          at wrapper (http://keyboard.gaiamobile.org:8080/common/test/mocha_generators.js:62:13)
09:13:31     INFO -          at run (http://keyboard.gaiamobile.org:8080/common/vendor/mocha/mocha.js:3709:7)
09:13:31     INFO -          at runTest (http://keyboard.gaiamobile.org:8080/common/vendor/mocha/mocha.js:4087:5)
09:13:31     INFO -          at (anonymous) (http://keyboard.gaiamobile.org:8080/common/vendor/mocha/mocha.js:4133:7)
09:13:31     INFO -          at next (http://keyboard.gaiamobile.org:8080/common/vendor/mocha/mocha.js:4013:7)
09:13:31     INFO -          at (anonymous) (http://keyboard.gaiamobile.org:8080/common/vendor/mocha/mocha.js:4022:7)
09:13:31     INFO -          at next (http://keyboard.gaiamobile.org:8080/common/vendor/mocha/mocha.js:3970:16)
09:13:31     INFO -          at (anonymous) (http://keyboard.gaiamobile.org:8080/common/vendor/mocha/mocha.js:3990:5)
09:13:31     INFO -          at (anonymous) (http://keyboard.gaiamobile.org:8080/common/vendor/mocha/mocha.js:4938:28)
09:13:31     INFO -  gaia-unit-tests TEST-UNEXPECTED-FAIL | keyboard/test/unit/jspinyin_test.js | jspinyin init | jspinyin is undefined

etc...
Blocks: 874510
Looking for help from the Gaia team; this problem has caused 1.4 to be closed.
Flags: needinfo?(yurenju.mozilla)
Flags: needinfo?(kgrandon)
Flags: needinfo?(felash)
FYI, I can revert the mozharness change from bug 874510, if that's what's causing the problem, but it isn't clear to me that it is, other than the timing of the change.
I already tried reverting the revision it started on and that didn't improve things (and I didn't expect it to based on what it changed). If you want more convincing that it's from the mozharness merge to production, I can kick off a run on a previously-green push as well.
So, I am controlling the version of Mozharness that's being used on Gaia-Try and it's running against http://hg.mozilla.org/users/jford_mozilla.com/mozharness/default

Does that branch have the mozharness merge to production that you're concerned by?  If it doesn't, we could kick off tests on the latest v1.4 commit using the latest v1.4 gecko builds to see if an older mozharness passes tests.
Looks like it does.
As long as I can continue to run my special commits, we could alter it to not have that merge
Oh, which merge do you suspect?
I've submitted

https://tbpl.mozilla.org/?tree=Gaia-Try&rev=d9b249f1eb00

This is testing reverting 35d2981a6365, which is what Ryan is suspecting is causing the breakage
Thanks for trying that revert John. I'll keep an eye on this thread and your run and will step-in if needed.
Flags: needinfo?(kgrandon)
Uplifted bug 998759 which wasn't on v1.4. Sorry about this, we should have done this long ago.
Flags: needinfo?(yurenju.mozilla)
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #3)
> I can kick off a run on a previously-green push as well.

Retriggered and failed in the same manner.
Depends on: 998759
Looks green now !
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.