Closed
Bug 1049790
Opened 11 years ago
Closed 11 years ago
[B2G][FTU][Date & Time] Changes to Continent and City are not displayed properly.
Categories
(Firefox OS Graveyard :: Gaia::First Time Experience, defect)
Firefox OS Graveyard
Gaia::First Time Experience
ARM
Gonk (Firefox OS)
Tracking
(blocking-b2g:2.0+, b2g-v1.3 unaffected, b2g-v1.4 fixed, b2g-v2.0 verified, b2g-v2.1 verified)
| Tracking | Status | |
|---|---|---|
| b2g-v1.3 | --- | unaffected |
| b2g-v1.4 | --- | fixed |
| b2g-v2.0 | --- | verified |
| b2g-v2.1 | --- | verified |
People
(Reporter: Marty, Assigned: aus)
References
()
Details
(Keywords: branch-patch-needed, regression, smoketest, Whiteboard: [systemsfe][p=3])
Attachments
(3 files, 1 obsolete file)
Description:
In the 'Date & Time' screen of the FTU, the user is able to Set the Continent and City. Changes made to these settings don't always update the display, requiring the user to switch back and forth several times for the change to show properly.
Repro Steps:
1) Update a Flame to 20140806000200
2) Progress through the FTU to the 'Date & Time' screen
3) Change the Continent and City settings.
Actual:
User choices are stored, but not displayed.
Expected:
User choices are displayed properly.
Environmental Variables:
Device: Flame 2.0 (319MB)
Build ID: 20140806000200
Gaia: 5ba22d458fdb63bd72c59de53c701d0efe35c1e2
Gecko: 6fbc60a80c6d
Version: 32.0 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Keywords: FTU, FTE, Date, Time, Continent, City, Update, Display
Repro frequency: ~50%
Link to failed test case: https://moztrap.mozilla.org/manage/case/6119/
See attached: video clip
| Reporter | ||
Comment 1•11 years ago
|
||
Issue does not seem to occur on Flame 2.0 (512MB)
Continent and City display updates properly.
Environmental Variables:
Device: Flame 2.0 (512MB)
Build ID: 20140806000200
Gaia: 5ba22d458fdb63bd72c59de53c701d0efe35c1e2
Gecko: 6fbc60a80c6d
Version: 32.0 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
-------------------------------------------------------------------
I am unable to see if Flame 2.1 is affected due to bug 1049149.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Comment 2•11 years ago
|
||
[Blocking Requested - why for this release]:
This was filed as a follow up to bug 1042388, it's a regression of a core feature and a smoketest blocker.
blocking-b2g: --- → 2.0?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Keywords: regression
Updated•11 years ago
|
blocking-b2g: 2.0? → 2.0+
Comment 4•11 years ago
|
||
Can someone try reproducing this with public Flame builds:
ftp://ftp.mozilla.org/pub/b2g/nightly/latest-mozilla-b2g32_v2_0-flame/
Keywords: qawanted
Comment 5•11 years ago
|
||
Well, one possibility is that my patch for bug 1042388 wasn't working after all, and that we hit what Tim describes in bug 1042388 comment 15:
> Also, this bug cannot be reproduced once I do another |adb reboot| in attempt to update ftu package
> again, so I highly doubt this bug should remain block. But QA would probably disagree because this
> apparently blocks the very important smoketest from continue.
If the patch was applied after flashing (with full startup of the phone), and then a reset-gaia was made, that could have led to a false positive.
I'm still unable to repro with TEF builds, but I'll try with the public one (that I actually didn't know existed!)
Flags: needinfo?(fernando.campo)
Comment 6•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #4)
> Can someone try reproducing this with public Flame builds:
>
> ftp://ftp.mozilla.org/pub/b2g/nightly/latest-mozilla-b2g32_v2_0-flame/
Btw - you'll want download the b2g-32.0.en-US.android-arm.tar.gz & gaia.zip, unzip the files in the same root directory, and download https://raw.githubusercontent.com/nhirata/fullflash/master/flash_Gg.sh. That should result in the following setup:
b2g/
gaia/
flash_Gg.sh
Then, run ./flash_Gg.sh.
Comment 7•11 years ago
|
||
So bad news, I am able to repro with the public build.
Better than bad news (still not good) is that I can try to work on it now.
Thanks for the link and explanation Jason
Comment 8•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #6)
> (In reply to Jason Smith [:jsmith] from comment #4)
> > Can someone try reproducing this with public Flame builds:
This issue DOES reproduce in this 2.0 Public build
Actual Results - not all changes are updated on the map (properly displayed)
additionally - not all the changes are 'stored' correctly - meaning that sometimes when I select a different option (ex: Asia) it will turn blue and get the blue checkmark, but when I hit OK the change is not reflected on the Date & Time page. Returning to the specific list (country or city) the new choice will still show highlighted blue with the checkmark and it can take several times going back and forth before the field is update. However; this only occurred during the first FTU encounter and did not repro later by launching the FTU from the developer menu
Device: Flame 2.0
Build ID: 20140807000201
Gaia: 8cc28fd31905a0ea2b2e15d13e80a0eab2feb1ba
Gecko: 25980b5120b0
Version: 32.0 (2.0)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Notes: Sim in, no wi-fi connection, no cellular data turned on
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Updated•11 years ago
|
Assignee: nobody → fernando.campo
Comment 10•11 years ago
|
||
I've also hit this problem with recent vendor builds for the flatfish tablet.
Comment 11•11 years ago
|
||
So I've been working on this for the last few days, tried more things during the weekend, and I'm out of ideas, still nothing works out, so some help would be most appreciated. To sum up:
- only happens on 273Mb flame. With more memory or other devices I'm unable to repro, no matter the build (didn't try on flatfish)
- only happens on fresh flash. The moment that we make a reset-gaia (even putting in the same gaia commit that it's already flashed, the problem disappears)
- only on MOZ builds, not on TEF side ones. I don't know if it might be related to the build process.
Here's what I've already tried:
- eliminated the duplicated call to tz_select - patch for bug bug 1042388 - in case the events were catched by the wrong object.
- trigger the changes before changing the timezone setting, in case they were not launched.
- created the 'moztimechange' listener before setting the timezone setting, in case it was too quick.
None of those solved the problem, and as I said, I'm out of ideas :(
If anybody have any clue, please jump in.
Comment 12•11 years ago
|
||
I'm reassigning myself to let room to anyone with more ideas, although I'll keep trying things.
ni? gregor so he can proxy my petition for help
Flags: needinfo?(anygregor)
Comment 13•11 years ago
|
||
Jeez, I need a break...I meant de-assigning
Assignee: fernando.campo → nobody
Comment 14•11 years ago
|
||
Marking qawanted here to see if this happens on 319 MB Flame on 1.4. If it doesn't, let's try getting a window here.
QA Whiteboard: [QAnalyst-Triage+]
Keywords: qawanted
Updated•11 years ago
|
Whiteboard: [systemsfe]
| Assignee | ||
Comment 16•11 years ago
|
||
I'll take a stab at this. What's the best way to repro? Looks like a fresh flash using Naoki's script is all it takes? Or do we need 273M memory profile as well?
Flags: needinfo?(aus)
Comment 17•11 years ago
|
||
(In reply to Ghislain Aus Lacroix [:aus] from comment #16)
> I'll take a stab at this. What's the best way to repro? Looks like a fresh
> flash using Naoki's script is all it takes? Or do we need 273M memory
> profile as well?
My understanding is that you need to flash a build from pvtbuilds (https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-b2g32_v2_0-flame/latest/) and try to reproduce this bug under a 319 MB Flame setting.
| Assignee | ||
Comment 18•11 years ago
|
||
Occurs as reported with 319M memory profile with 2.0 and 2.1.
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → aus
Status: NEW → ASSIGNED
Target Milestone: --- → 2.1 S2 (15aug)
Updated•11 years ago
|
QA Contact: ddixon
Comment 19•11 years ago
|
||
Following results checked on device with 319 MB memory.
DOES occur in Flame 1.4 with v122 base image.
Device: Flame 1.4
Build ID: 20140811081112
Gaia: d47fecdcaa4aefb754561114edd22fb23a92b98d
Gecko: fbee340d0830
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
DOES occur in Flame 1.4 with v123 base image.
Device: Flame 1.4
Build ID: 20140811081112
Gaia: d47fecdcaa4aefb754561114edd22fb23a92b98d
Gecko: fbee340d0830
Version: 30.0 (1.4)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Comment 20•11 years ago
|
||
Duane - Can you also check the base image as well?
Comment 21•11 years ago
|
||
DOES NOT occur on v122, v123 base images with 319 MB memory.
Device: Flame 1.3
Build ID: 20140627162151
Gaia: 5c43d012a9351e8aaeacda0b87b0886b7f67d33d
Gecko: e181a36ebafaa24e5390db9f597313406edfc794
Version: 28.0 (1.3)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0
Device: Flame 1.3
Build ID: 20140616171114
Gaia: e1b7152715072d27e0880cdc6b637f82fa42bf4e
Gecko: e181a36ebafaa24e5390db9f597313406edfc794
Version: 28.0 (1.3)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v1.3:
--- → unaffected
Flags: needinfo?(jmitchell)
Keywords: qawanted
Updated•11 years ago
|
| Assignee | ||
Comment 22•11 years ago
|
||
After investigating into this yesterday and this morning it would appear that the moztimechange event is delivered late, somehow. I only get the event the time zone is changed again. There's something weird with the event queue which is causing the event to get stuck until a new event of the same type is put into it.
| Assignee | ||
Comment 23•11 years ago
|
||
Hah! Awesome, well, that was easier than I thought. Pull Request incoming which will cover both 2.1 and 2.0.
| Assignee | ||
Comment 24•11 years ago
|
||
No one other than you has reviewed code for this in over a year so, lucky you! :)
Attachment #8471940 -
Flags: review?(francisco)
Updated•11 years ago
|
Keywords: qaurgent,
regressionwindow-wanted
| Assignee | ||
Comment 25•11 years ago
|
||
Attachment #8471973 -
Flags: review?(francisco)
| Assignee | ||
Updated•11 years ago
|
Attachment #8471940 -
Flags: review?(francisco) → review?(dflanagan)
| Assignee | ||
Updated•11 years ago
|
Attachment #8471973 -
Flags: review?(francisco) → review?(dflanagan)
| Assignee | ||
Updated•11 years ago
|
Attachment #8471940 -
Flags: review?(dflanagan) → review?(fernando.campo)
| Assignee | ||
Updated•11 years ago
|
Attachment #8471973 -
Flags: review?(dflanagan) → review?(fernando.campo)
Comment 27•11 years ago
|
||
Comment on attachment 8471973 [details] [review]
Pull Request (master) - Use one listener for moztimechange
Code is good, and it seems to work (but again, everything seems to work when making reset-gaia :D)
Hopefully this should work when flashing a clean build, thanks.
Attachment #8471973 -
Flags: review?(fernando.campo) → review+
Comment 28•11 years ago
|
||
Comment on attachment 8471940 [details] [review]
Pull Request (v2.0 or less) - Use one listener for moztimechange
Patch for 2.0 is good to go too.
Attachment #8471940 -
Flags: review?(fernando.campo) → review+
| Assignee | ||
Comment 29•11 years ago
|
||
Commit (v2.0): https://github.com/mozilla-b2g/gaia/commit/408e24a54fb13217428fa9387ca01044a1ea3da4
Commit (master): https://github.com/mozilla-b2g/gaia/commit/c9127a4a9b41f99675b0ad746832bf1f511493d9
status-b2g-v2.1:
--- → fixed
| Assignee | ||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•11 years ago
|
Whiteboard: [systemsfe] → [systemsfe][p=3]
| Assignee | ||
Comment 30•11 years ago
|
||
My change for 2.0 doesn't apply cleanly to 1.4 so I'm creating yet another patch for that branch.
| Assignee | ||
Comment 31•11 years ago
|
||
Too big of a difference in line numbers prevented the 2.0 PR from applying on 1.4 so I fixed the merged conflicts by hand and created this PR.
Attachment #8473240 -
Flags: review+
| Assignee | ||
Comment 32•11 years ago
|
||
Commit (v1.4): https://github.com/mozilla-b2g/gaia/commit/ab9a57d204c8c06cccc70cb7190da789fe17a3cb
For my flatfish friends. :)
This broke gaia-linter on 2.0: https://tbpl.mozilla.org/php/getParsedLog.php?id=45966627&tree=Mozilla-B2g32-v2.0
13:27:06 INFO - Running command: ['make', 'lint'] in /builds/slave/test/gaia
13:27:06 INFO - Copy/paste: make lint
13:27:06 INFO - Calling ['make', 'lint'] with output_timeout 330
13:27:06 INFO - NO_XFAIL=1 make -k gjslint hint
13:27:07 INFO - make[1]: Entering directory `/builds/slave/test/gaia'
13:27:07 INFO - # gjslint --disable 210,217,220,225 replaces --nojsdoc because it's broken in closure-linter 2.3.10
13:27:07 INFO - # http://code.google.com/p/closure-linter/issues/detail?id=64
13:27:07 INFO - Running gjslint...
13:28:17 INFO - 542 files checked, no errors found.
13:28:17 INFO - Note: gjslint only checked the files that are xfailed for jshint.
13:28:17 INFO - Running jshint...
13:30:54 ERROR - TEST-UNEXPECTED-FAIL | shared/js/tz_select.js | line 208, col 8, Missing semicolon.
13:30:54 INFO - shared/js/tz_select.js: line 208, col 8, Missing semicolon. (ERROR)
13:30:54 ERROR - TEST-UNEXPECTED-FAIL | shared/js/tz_select.js | line 231, col 9, Missing semicolon.
13:30:54 INFO - shared/js/tz_select.js: line 231, col 9, Missing semicolon. (ERROR)
13:30:54 INFO - 2 errors (13275 xfailed)
13:30:54 INFO - Please consult https://github.com/mozilla-b2g/gaia/tree/master/build/jshint/README.md to get some information about how to fix jshint issues.
13:30:54 INFO - TEST-UNEXPECTED-FAIL | make lint | make[1]: *** [hint] Error 1
13:30:54 INFO - make[1]: *** [hint] Error 1
13:30:54 INFO - make[1]: Leaving directory `/builds/slave/test/gaia'
13:30:54 INFO - TEST-UNEXPECTED-FAIL | make lint | make: *** [lint] Error 2
13:30:54 INFO - make: *** [lint] Error 2
13:30:54 ERROR - Return code: 2
13:30:54 INFO - TinderboxPrint: gaia-lint: <em class="testfail">4 errors</em>
13:30:54 ERROR - Tests exited with return code 2: harness failures
13:30:54 ERROR - # TBPL FAILURE #
Flags: needinfo?(aus)
| Assignee | ||
Comment 34•11 years ago
|
||
(In reply to Wes Kocher (:KWierso) from comment #33)
> This broke gaia-linter on 2.0:
> https://tbpl.mozilla.org/php/getParsedLog.php?id=45966627&tree=Mozilla-B2g32-
> v2.0
> 13:27:06 INFO - Running command: ['make', 'lint'] in
> /builds/slave/test/gaia
> 13:27:06 INFO - Copy/paste: make lint
> 13:27:06 INFO - Calling ['make', 'lint'] with output_timeout 330
> 13:27:06 INFO - NO_XFAIL=1 make -k gjslint hint
> 13:27:07 INFO - make[1]: Entering directory `/builds/slave/test/gaia'
> 13:27:07 INFO - # gjslint --disable 210,217,220,225 replaces --nojsdoc
> because it's broken in closure-linter 2.3.10
> 13:27:07 INFO - #
> http://code.google.com/p/closure-linter/issues/detail?id=64
> 13:27:07 INFO - Running gjslint...
> 13:28:17 INFO - 542 files checked, no errors found.
> 13:28:17 INFO - Note: gjslint only checked the files that are xfailed
> for jshint.
> 13:28:17 INFO - Running jshint...
> 13:30:54 ERROR - TEST-UNEXPECTED-FAIL | shared/js/tz_select.js | line
> 208, col 8, Missing semicolon.
> 13:30:54 INFO - shared/js/tz_select.js: line 208, col 8, Missing
> semicolon. (ERROR)
> 13:30:54 ERROR - TEST-UNEXPECTED-FAIL | shared/js/tz_select.js | line
> 231, col 9, Missing semicolon.
> 13:30:54 INFO - shared/js/tz_select.js: line 231, col 9, Missing
> semicolon. (ERROR)
> 13:30:54 INFO - 2 errors (13275 xfailed)
> 13:30:54 INFO - Please consult
> https://github.com/mozilla-b2g/gaia/tree/master/build/jshint/README.md to
> get some information about how to fix jshint issues.
> 13:30:54 INFO - TEST-UNEXPECTED-FAIL | make lint | make[1]: *** [hint]
> Error 1
> 13:30:54 INFO - make[1]: *** [hint] Error 1
> 13:30:54 INFO - make[1]: Leaving directory `/builds/slave/test/gaia'
> 13:30:54 INFO - TEST-UNEXPECTED-FAIL | make lint | make: *** [lint]
> Error 2
> 13:30:54 INFO - make: *** [lint] Error 2
> 13:30:54 ERROR - Return code: 2
> 13:30:54 INFO - TinderboxPrint: gaia-lint: <em class="testfail">4
> errors</em>
> 13:30:54 ERROR - Tests exited with return code 2: harness failures
> 13:30:54 ERROR - # TBPL FAILURE #
I already pushed a specific fix for this issue. It should recover when the next build cycles (iirc).
Flags: needinfo?(aus)
Comment 35•11 years ago
|
||
marty, please verify fix on 2.0 and master. thanks.
Flags: needinfo?(mshuman)
Keywords: verifyme
| Reporter | ||
Comment 36•11 years ago
|
||
Verified Fixed. Issue no longer occurs on Flame 1.4, Flame 2.0, or Flame 2.1 at either 512MB or 319MB.
Continent and City display updates properly.
Environmental Variables:
Device: Flame 1.4
Build ID: 20140815063005
Gaia: ab9a57d204c8c06cccc70cb7190da789fe17a3cb
Gecko: 3da3115ee33b
Version: 30.0 (1.4)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Environmental Variables:
Device: Flame 2.0
Build ID: 20140815000200
Gaia: 295c7f50707372e5af6d8e83148d2d970076dfd6
Gecko: 879c5208084f
Version: 32.0 (2.0)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Environmental Variables:
Device: Flame Master
Build ID: 20140815040204
Gaia: 9979fccc6321be72cd17370f3a20c65bc376af33
Gecko: c9f8cc9ce89c
Version: 34.0a1 (Master)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(mshuman) → needinfo?(pbylenga)
Updated•11 years ago
|
Comment 37•11 years ago
|
||
Reverted from v1.4 for causing frequent Gij failures (confirmed by 30+ green retriggers on the push prior).
v1.4: https://github.com/mozilla-b2g/gaia/commit/21bec64497dc06a7f12071d573570ba8fea598ae
https://tbpl.mozilla.org/php/getParsedLog.php?id=46069500&tree=Mozilla-B2g30-v1.4
Updated•11 years ago
|
Flags: needinfo?(aus)
Keywords: branch-patch-needed
| Assignee | ||
Comment 38•11 years ago
|
||
Thanks for backing that out Ryan, I totally forgot to check up on it. :(
I should have a branch patch that doesn't break the world soon...
Flags: needinfo?(aus)
| Assignee | ||
Comment 39•11 years ago
|
||
Attachment #8473240 -
Attachment is obsolete: true
| Assignee | ||
Comment 40•11 years ago
|
||
And, we're all green!
https://tbpl.mozilla.org/?rev=9e6b60dae6f2bffffb58957b52d396f1c1a8d714&tree=Gaia-Try
Commit (v1.4): https://github.com/mozilla-b2g/gaia/commit/eb6f48b786999b833b4175cfd5bb9ef22227e65f
Fixed on v1.4.
You need to log in
before you can comment on or make changes to this bug.
Description
•