897813 - [Buri][FOTA][Call log]The call time dispaly abnormal after upgrading succeed.

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Dialer, defect, P1)

Description

[sync-1]

AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.164
 Firefox os  v1.1
 Mozilla build ID:20130715070218
 
 Created an attachment (id=468341)
 0724
 
 DEFECT DESCRIPTION:
 The call time dispaly abnormal after upgrading succeed.
 
 REPRODUCING PROCEDURES:
 Precondition:
 Have some call logs before upgrading
 
 1.Download diff package,and install it,it will upgrade succeed.
 2.Then click Phone,enter the call log,fing the call time display abnormal. --KO
 
 EXPECTED BEHAVIOUR:
 The call time can display normal after upgrading succeed.
 
 ASSOCIATE SPECIFICATION:
 
 TEST PLAN REFERENCE:
 
 TOOLS AND PLATFORMS USED:
 
 USER IMPACT:
 Medium
 
 REPRODUCING RATE:
 3/3
 
 For FT PR, Please list reference mobile's behavior:

Comment 1

[sync-1]

Clone from brother

Comment 2

[sync-1]

Attachment: 0724

Comment 3

[sync-1]

Clone from brother

Comment 4

[sync-1]

Attachment: 493690-adblog

Comment 5

[Alex Keybl [:akeybl]]

STR does not appear to have critical user impact.

Comment 6

[Amelie Kong]

This is the bug after upgrade from 1.0.1 to 1.1, I think it has quite big impact on users. as all the time information is lost for all call logs.

Nominate it as Leo?

Comment 7

[Andrew Overholt [:overholt]]

This seems bad enough to block v1.1 (data loss).

Comment 8

[:gerard-majax]

This bug is quite old, we did a lot of fixes recentlt on the call log upgrade path, can you ensure that it is still present with recent gecko and gaia ? Like of today for example ?

Comment 9

[:gerard-majax]

I'm thinking to bug 862385 which landed on july 14th as far as I can say, and since the build in this bug is dated july 15th ... :)

Comment 10

[Darren]

If possible, to be able to check this issue we will need the steps/ link/ update channel used to go from 1.0.1 - 1.1 that was used to simulate the issue. 

Thank you

Comment 11

[Jason Smith [:jsmith]]

(In reply to Darren from comment #10)
> If possible, to be able to check this issue we will need the steps/ link/
> update channel used to go from 1.0.1 - 1.1 that was used to simulate the
> issue. 
> 
> Thank you

The QA Wanted request in this case is asking to test an update path from 1.01 --> 1.1 in which the 1.01 build had some calls populated in the call log. You should check that the time was remained correct from the 1.01 to 1.1 upgrade.

Comment 12

[Askeing Yen[:askeing][:fyen]]

Device: Unagi
Pvt v1.0.1
  Gaia:     054cdc27404e2daca91d3065d9783681032b2151
  Gecko:    http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/9c62297d11b0
  BuildID   20130814043202
  Version   18.0
to v1.1.0 http://update.boot2gecko.org/unagi/1.1.0/nightly/update.xml
  Gaia:     dd3959fa74e356a528daa76ffee14c2c728a4b56
  Gecko:    http://hg.mozilla.org/releases/mozilla-b2g18/rev/15813d776a69
  BuildID   20130814041202
  Version   18.0

WFM on unagi from 1.0.1 to 1.1.0.

Comment 13

[Jason Smith [:jsmith]]

Thanks Askeing. Works for me per comment 12.

Comment 14

[Hubert Lu[:hlu] <[e-mail]>]

Device: Inari
Pvt v1.0.1
Gaia:     054cdc27404e2daca91d3065d9783681032b2151
  B-D     2013-07-06 19:39:29
Gecko:    http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/9c62297d11b0
BuildID   20130814043202
Version   18.0

to v1.1.0 http://update.boot2gecko.org/unagi/1.1.0/nightly/update.xml
Gaia:     0f1f1ab0ab31a1df8a780baa048b5e7b2854205d
  B-D     2013-08-15 06:32:03
Gecko:    http://hg.mozilla.org/releases/mozilla-b2g18/rev/692d3414bb12
BuildID   20130815041201
Version   18.0

Work for me on Inari from 1.0.1 to 1.1.0.

Comment 15

[Mingming ZHAO]

Dears,

How about this issue now?