Closed Bug 1068178 Opened 6 years ago Closed 6 years ago

end to end call test broken by pending call view cahnges

Categories

(Hello (Loop) :: General, defect)

x86
All
defect
Not set
normal

Tracking

(firefox34 fixed, firefox35 fixed)

RESOLVED FIXED
mozilla35
Tracking Status
firefox34 --- fixed
firefox35 --- fixed

People

(Reporter: dmose, Assigned: dmose)

References

Details

(Whiteboard: [loop-uplift])

Attachments

(1 file, 1 obsolete file)

No description provided.
Assignee: nobody → dmose
Comment on attachment 8490251 [details] [diff] [review]
Fix Loop functional test bustage, rs=Standard8, NPOTB, so DONTBUILD

Review of attachment 8490251 [details] [diff] [review]:
-----------------------------------------------------------------

rs=Standard8 over IRC
Attachment #8490251 - Flags: review+
Blocks: 1000237
https://hg.mozilla.org/mozilla-central/rev/ad92c85dce35
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
While we don't technically have to uplift this, I'd strongly suggest we do, so that we can easily check that other uplifted changes haven't broken at least the basic functionality.  Adding [loop-uplift] whiteboard markup.
Whiteboard: [loop-uplift]
Flags: qe-verify-
Comment on attachment 8490251 [details] [diff] [review]
Fix Loop functional test bustage, rs=Standard8, NPOTB, so DONTBUILD

Approval Request Comment
Uplift request for patches staged and tested on Fig
Attachment #8490251 - Flags: approval-mozilla-aurora?
Comment on attachment 8490251 [details] [diff] [review]
Fix Loop functional test bustage, rs=Standard8, NPOTB, so DONTBUILD

I worked with Randell and Maire on uplifting a large number of Loop bugs at once. All of the bugs have been staged on Fig and tested by QE before uplift to Aurora. As well, all of the bugs are isolated to the Loop client. Randell handled the uplift with my approval. I am adding approval to the bug after the fact for bookkeeping.
Attachment #8490251 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
You need to log in before you can comment on or make changes to this bug.