Closed Bug 787578 Opened 9 years ago Closed 9 years ago

B2G Updates: Get updater automated tests running for B2G

Categories

(Firefox OS Graveyard :: General, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:+, b2g18 fixed)

RESOLVED FIXED
B2G C2 (20nov-10dec)
blocking-basecamp +
Tracking Status
b2g18 --- fixed

People

(Reporter: marshall, Assigned: ahal)

References

Details

I can turn these on any time you tell me they're ready.
Updates are very important and these large sets warrant a blocking+ IMO.
blocking-basecamp: ? → +
Component: Application Update → General
Product: Toolkit → Boot2Gecko
Depends on: 797164
Depends on: 790677
I've worked on these tests a lot before and there will be some work here relating to signing, so I'll take this bug
Assignee: marshall → netzen
Depends on: 797162
Priority: -- → P1
Unassigned based on dependencies
Assignee: netzen → nobody
Removing mochitest-chrome as a dep, since the existing mochitest-chrome tests for the updater are Firefox-specific.
No longer depends on: 797164
Has there been any progress here?  Are we still blocked on getting the xpcshell tests going?
Flags: needinfo?
I think this is blocked on the dependent bug which looks like it should land soon.
Flags: needinfo?
Brian, what are the next steps here?
Could you provide logs for the failing tests? Are other xpcshell-tests up and running now?
(In reply to Jonathan Griffin (:jgriffin) from comment #5)
> Removing mochitest-chrome as a dep, since the existing mochitest-chrome
> tests for the updater are Firefox-specific.
Note that the mochitest-chrome tests are actually toolkit specific and work with Firefox, Thunderbird, and SeaMonkey.
Assignee: nobody → netzen
dougt, can you help out getting the info requested in comment #9?
Marking for C2, given this meets the criteria of known P1/P2 blocking-basecamp+ bugs at the end of C1.
Target Milestone: --- → B2G C2 (20nov-10dec)
(In reply to Brian R. Bondy [:bbondy] from comment #9)
> Could you provide logs for the failing tests? Are other xpcshell-tests up
> and running now?

Could someone answer the second part of this?  Are other xpcshell-tests up and running now?
ahal is working on getting xpcshell tests for B2G running on TPBL, see bug 797153
CC akeybl: See Comment 14
Then I suggest that should also be a C2 blocker. 
Unassigned myself again since I can't work on it.
Assignee: netzen → nobody
Depends on: 797153
Bug 797153 was just a small piece, there's still a lot of work to be done. But if I drop everything I think I can get xpcshell tests running by C2. But there are still some unknowns to me (e.g bug 815641)
Depends on: 809233
I think this should be re-evaluated for consideration for C2 given the last couple comments.
The biggest issue blocking me is bug 816086. If I can get that figured out by the end of the week I think there is a decent chance of at least getting xpcshell tests running on cedar by Dec 10th (main tracking bug for that is bug 809233).
Depends on: 816086
Andrew, assigning to you as it looks like you're working on this.
Assignee: nobody → ahalberstadt
Feel free to file followups for specific app update xpcshell test failures to me.
No longer depends on: 816086
Depends on: 817651
(In reply to Marshall Culpepper [:marshall_law] from comment #0)
> - http://dxr.mozilla.org/mozilla-central/toolkit/mozapps/update/test/
> - http://dxr.mozilla.org/mozilla-central/toolkit/mozapps/update/test_svc/

These two sets of test don't seem to be in the tests.zip. Filed bug 817651 to get them added.
Update: xpcshell looks to be on track to ready to go on m-c by monday (+ time for releng to change and update the configs)

However that still won't change the fact that the update tests aren't being added to the tests.zip because MOZ_UPDATER isn't being defined in the build (bug 817651)
:ahal, there seems to be a bunch of dependency here.  what's the ETA here since this missed the C2 milestone?
Andrew has previously told me that he expected this work to be complete and deployed by mid week (roughly Wednesday). Andrew, is this still accurate?
(In reply to Lawrence Mandel [:lmandel] from comment #24)
> Andrew has previously told me that he expected this work to be complete and
> deployed by mid week (roughly Wednesday). Andrew, is this still accurate?

Yep, they're running green on Cedar. Just need to land a manifest change on the core branches and wait for releng to enable the config (which is already reviewed).
Just waiting for the latest patch in bug 807125 to land
All has landed, they should go live on all branches either today or tomorrow.
xpcshell tests are now unhidden on green on inbound (and m-c after next merge) and aurora. Unfortunately on b2g18 they're hitting bug 811830 for some reason. There is a separate bug I'm working on (bug 821012) which I believe will workaround the issue in bug 811830.

In the mean time there are several update tests that seem to fail which are outside of my domain knowledge to look into.

* toolkit/mozapps/update/test/unit/test_0030_general.js
* toolkit/mozapps/update/test/unit/test_0081_prompt_uiAlreadyOpen.js
* toolkit/mozapps/update/test/unit/test_bug595059.js
* all tests in toolkit/mozapps/update/test/unit/xpcshell_updater.ini

I haven't filed bugs for these yet, but if someone does please make it block bug 820380
Depends on: 821333
The problem on the mozilla-b2g18 branch isn't bug 811830 after all, it's just that the version of remotexpcshelltests.py is out of date. I filed bug 821333 to fix the problem.
Filed bug 821343 and bug 821344 to look into the test failures in comment 28
Depends on: 821720
These are now running on all branches including b2g18 (though they are still hidden due to one of the tests timing out, will disable it soon).

This bug is more or less finished from my point of view. Lets use bug 821343 and bug 821344 to track progress on fixing remaining problems with the update tests.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.