Re: [b2g] Sensor events when the screen is off via wakelock. Good idea or?

2014-07-21 Thread Chelsea Wu
Hi, Jonas and Jan,

Good Day!

Thanks a lot for this discussion thread. This is quite related to what I am
working on now.

So far I am applying a wakelock for screen with camera function turned on;
however, my ultimate ideal solution is to have vibration active while
screen is still off in the scenario that it's at certain timing but not yet
reached certain point on GPS...

I am still looking for better solution or potential ways, hopefully it not
a complete out-of-the-question.. let's keep this discussion updated if
there is new ideas! :)

BR,
Chelsea


On Mon, Jul 14, 2014 at 6:14 AM, Jonas Sicking jo...@sicking.cc wrote:


 On Jul 13, 2014 8:59 AM, Jan Jongboom janjongb...@gmail.com wrote:
   Can I ask what type of thing you are trying to build?
  
   We do actually have a permission for ability to use sensor API even
 in background. That permission should give you ability to use sensors
 while holding the CPU lock. Though the permission might only be granted to
 privileged apps. And I'm not sure its used much so might no longer work.
  
  
   / Jonas
 
  In general I'd say for stuff like navigation apps if you're on bike.
 Makes no sense to have the screen on in that case, but I would want data
 from the GPS and maybe use vibrate to notify users when they need to turn.
 
  Or an app like Moves that tracks what you're doing (biking, cycling,
 anything). We can run it in the background through alarms but can't track
 anything.

 Yeah, a permission I think would solve access to sensors and GPS.

 I don't have a great solution for vibration. What we are basically looking
 for is a way to notify the user without brining up a notification. Or at
 least make the notification less persistent.

 Maybe simply use the notification API, but delete the notification as soon
 as your app becomes visible.

 / Jonas

 ___
 dev-b2g mailing list
 dev-b2g@lists.mozilla.org
 https://lists.mozilla.org/listinfo/dev-b2g


___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g


[b2g] 07/21/2014 Dolphin 1.4 Mozilla RIL Smoke Test Results - 48/48 tests passed, 0 blocker

2014-07-21 Thread Peipei Cheng
48 out of 48 tests passed for the 2014-07-21 Dolphin V1.4 Mozilla RIL
Build.

Mozilla RIL Build Smoketest Results:

Moztrap test result link:  
https://moztrap.mozilla.org/results/cases/?filter-run=4754

Moztrap test run link:  https://moztrap.mozilla.org/runtests/run/4754/env/27895/

New Bugs Breaking the Smoketests:

None was found.

Existing Bugs Breaking the Smoketests:

None was found.

New Issues Not Breaking the Smoketests:

None was found.

Tests Were Performed With:

BuildID:*20140721000201*

Gaia:*621d152f89347c79619aa909ad62cc2ac9d3ab5b*

Gecko:https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/83b7be7fb33f

Build Location:
https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-b2g30_v1_4-dolphin/2014/07/2014-07-21-00-02-01/

1 reboot

0 crashes

Sincerely,

Mozilla QA Team

___

Qa-b2g mailing list

qa-...@mozilla.org

https://mail.mozilla.org/listinfo/qa-b2g

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g


[b2g] 07/21/2014 Flame Gaia-ui Automation v2.0 Mozilla RIL Build 38/39 smoketests, 80/82 non-smoketests

2014-07-21 Thread florin.strugariu

*Smoketests:*
*
Test failures- 0***replicable manually**:**

 * [Not replicable manually] test_play_3gp_video.TestPlay3GPVideo -
   *Bug 1024517* https://bugzilla.mozilla.org/show_bug.cgi?id=1024517
   -[Flame] Investigate Video app test failures

*Expected failures / disabled tests:*

 * [Disabled] test_setup_and_send_active_sync_email.py - *Bug 1028192*
   https://bugzilla.mozilla.org/show_bug.cgi?id=1028192 - Problems
   with ActiveSync accounts
 * [Disabled] test_receive_active_sync_email.py - *Bug 1028192*
   https://bugzilla.mozilla.org/show_bug.cgi?id=1028192 - Problems
   with ActiveSync accounts

*
Non-smoketests - 0***replicable manually*:**

Test failures:*

 * [Not replicable manually]
   test_fmradio_find_stations.TestFMRadioFindStations -
 * [Not replicable manually] test_play_webm_video.TestPlayWebMVideo -
   *Bug 1024517* https://bugzilla.mozilla.org/show_bug.cgi?id=1024517
   -[Flame] Investigate Video app test failures

*Expected failures / disabled tests:*

 * [Disabled] test_settings_sim_manager.py - Disabled because run the
   device with 1 SIM only
 * [Disabled] test_privileged_app_contacts_prompt.py - *Bug 1021732
   https://bugzilla.mozilla.org/show_bug.cgi?id=1021732* - [Flame]
   Re-enable test_privileged_app_contacts_prompt
   https://bugzilla.mozilla.org/show_bug.cgi?id=1024513


*Build under test:

*Gaia  8cb1a949f2e9650bb2c5598e78a6f24a58bbaf97
Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/4bd4b0ae7bbe
BuildID   20140721000201
Version   32.0a2
ro.build.version.incremental=109
ro.build.date=Mon Jun 16 16:51:29 CST 2014
B1TC00011220*


Summary:*

Smoketests:

39 tests ran in 2202 seconds.
38 passed, 88 skipped, 0 failed, 1 errors.
0 expected failures, 0 unexpected passes.

Non-smoketests:

82 tests ran in 3767 seconds.
80 passed, 45 skipped, 0 failed, 2 errors.
0 expected failures, 0 unexpected passes.




___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g


[b2g] [Peak] device storage does not work properly

2014-07-21 Thread Jovan Gerodetti
Hi,

While I experimented with my own builds and the official Geeksphone builds,
I recognized that with an official build everything works fine but with my
builds the device storage does not work as it should.

1. The device detects no internal storage.
2. In SettingsMedia Storage it displays Internal (actually my SD-Card) and
two SD-Card slots even though the Peak has only one SD-Card slot.
3. I have to select internal as default storage to be able to save files
(with SD-Card I get requested to insert a SD-Card)
3. The rescanning of the media apps does not work. If they have no indexDB
they will find every file and after that they doesn't recognize any
change...
4. File browser apps take much longer to display the directory indexes.

This all works with the official builds but not with my own builds. I
experienced this problem since I create my own builds (since v1.4).
Can someone think of anything how this could be fixed?


-- Jovan
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g


Re: [b2g] [Peak] device storage does not work properly

2014-07-21 Thread Dave Hylands
Hi Jovan, 

Device Storage gets its knowledge of which volumes exist from 2 sources. 

One is from the vold service. If you can get into an adb root shell (either use 
adb shell followed by su or adb root followed by adb shell) then you should be 
able to get vold's notion of volumes with this command: 

vdc volume list 

Device Storage also reads the /system/etc/volume.cfg file. I would expect this 
file to not be present on a geeksphone. 

If your vdc volume list looks wonky, then we can further investigate along 
those lines. 
vold determines its volumes by looking at /system/etc/vold.fstab (and I seem to 
recall older versions may have used another file as well, but I don't recall 
off the top of my head). 

Dave Hylands 

- Original Message -

 From: Jovan Gerodetti titannanom...@gmail.com
 To: dev-b2g@lists.mozilla.org
 Sent: Monday, July 21, 2014 11:02:47 AM
 Subject: [b2g] [Peak] device storage does not work properly

 Hi,

 While I experimented with my own builds and the official Geeksphone builds, I
 recognized that with an official build everything works fine but with my
 builds the device storage does not work as it should.

 1. The device detects no internal storage.
 2. In SettingsMedia Storage it displays Internal (actually my SD-Card) and
 two SD-Card slots even though the Peak has only one SD-Card slot.
 3. I have to select internal as default storage to be able to save files
 (with SD-Card I get requested to insert a SD-Card)
 3. The rescanning of the media apps does not work. If they have no indexDB
 they will find every file and after that they doesn't recognize any
 change...
 4. File browser apps take much longer to display the directory indexes.

 This all works with the official builds but not with my own builds. I
 experienced this problem since I create my own builds (since v1.4).
 Can someone think of anything how this could be fixed?

 -- Jovan

 ___
 dev-b2g mailing list
 dev-b2g@lists.mozilla.org
 https://lists.mozilla.org/listinfo/dev-b2g
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g


Re: [b2g] [Peak] device storage does not work properly

2014-07-21 Thread Jovan Gerodetti
the volume list looks like this:

root@android:/ # vdc volume list
 110 sdcard /mnt/sdcard 4
 110 emmc /mnt/emmc 0
 110 fat /mnt/fat 0
 200 Volumes listed.


As you thought, /system/etc/volume.cfg does not exist and
/system/etc/vold.fstab
contains this:

 dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.1/mmc_host

 dev_mount emmc /mnt/emmc 18 /devices/platform/msm_sdcc.3/mmc_host/mmc0

 dev_mount fat /mnt/fat auto /devices/virtual/block/loop7


In addition I found this with adb logcat | grep Vold:

 I/Vold(  126): Vold 2.1 (the revenge) firing up
 I/Vold(  126): Load /etc/vold.origin.fstab. Do not use internal emmc
 partition.
 D/Vold(  126): Volume sdcard state changing -1 (Initializing) - 0
 (No-Media)
 D/Vold(  126): Volume emmc state changing -1 (Initializing) - 0
 (No-Media)
 D/Vold(  126): Volume fat state changing -1 (Initializing) - 0
 (No-Media)
 D/Vold(  126): Volume sdcard state changing 0 (No-Media) - 2 (Pending)
 D/Vold(  126): Volume sdcard state changing 2 (Pending) - 1
 (Idle-Unmounted)
 D/VoldCmdListener(  126): volume list
 D/VoldCmdListener(  126): volume mount sdcard
 I/Vold(  126): /dev/block/vold/179:33 being considered for volume
 sdcard
 D/Vold(  126): Volume sdcard state changing 1 (Idle-Unmounted) - 3
 (Checking)
 W/Vold(  126): Skipping fs checks
 I/Vold(  126): Device /dev/block/vold/179:33, target /mnt/sdcard
 mounted @ /mnt/secure/staging
 D/Vold(  126): Volume sdcard state changing 3 (Checking) - 4 (Mounted)
 D/VoldCmdListener(  126): volume list



-- Jovan



2014-07-21 20:45 GMT+02:00 Dave Hylands dhyla...@mozilla.com:

 Hi Jovan,

 Device Storage gets its knowledge of which volumes exist from 2 sources.

 One is from the vold service. If you can get into an adb root shell
 (either use adb shell followed by su or adb root followed by adb shell)
 then you should be able to get vold's notion of volumes with this command:

 vdc volume list

 Device Storage also reads the /system/etc/volume.cfg file. I would expect
 this file to not be present on a geeksphone.

 If your vdc volume list looks wonky, then we can further investigate along
 those lines.
 vold determines its volumes by looking at /system/etc/vold.fstab (and I
 seem to recall older versions may have used another file as well, but I
 don't recall off the top of my head).

 Dave Hylands


 --

 *From: *Jovan Gerodetti titannanom...@gmail.com
 *To: *dev-b2g@lists.mozilla.org
 *Sent: *Monday, July 21, 2014 11:02:47 AM
 *Subject: *[b2g] [Peak] device storage does not work properly


 Hi,

 While I experimented with my own builds and the official Geeksphone
 builds, I recognized that with an official build everything works fine but
 with my builds the device storage does not work as it should.

 1. The device detects no internal storage.
 2. In SettingsMedia Storage it displays Internal (actually my SD-Card)
 and two SD-Card slots even though the Peak has only one SD-Card slot.
 3. I have to select internal as default storage to be able to save files
 (with SD-Card I get requested to insert a SD-Card)
  3. The rescanning of the media apps does not work. If they have no
 indexDB they will find every file and after that they doesn't recognize any
 change...
  4. File browser apps take much longer to display the directory indexes.

 This all works with the official builds but not with my own builds. I
 experienced this problem since I create my own builds (since v1.4).
 Can someone think of anything how this could be fixed?


 -- Jovan

 ___
 dev-b2g mailing list
 dev-b2g@lists.mozilla.org
 https://lists.mozilla.org/listinfo/dev-b2g



___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g


Re: [b2g] [Peak] device storage does not work properly

2014-07-21 Thread Dave Hylands
Hi Jovan, 

So this means that vold reports 3 volumes, sdcard, emcc, and fat which is why 
you see 3 storages in the settings app. I think that the production peak only 
supported a single storage area (regardless of whether there were more). New 
builds of FxOS support multiple volumes, so it's really just about getting 
things setup properly. 

It looks like fat is some type of loop mount of another filesystem (many 
internal filesystems do this). 

I think that FxOS normally expects the volume named sdcard to be the internal 
one, and anything else to be an external volume (either a physical sdcard or a 
USB thumb drive). 

I don't have a peak, so I'm not sure what the production vold.fstab looks like. 
I didn't think that the geeksphones had internal/external media storage areas. 
I though that they just had the physical sdcard (but I could be wrong). 
/data is an internal storage area for apps, but not for device storage. 

It would probably be useful to look at the output of the mount command from 
your phone and the production phone as well. 

Dave Hylands 

- Original Message -

 From: Jovan Gerodetti titannanom...@gmail.com
 To: Dave Hylands dhyla...@mozilla.com
 Cc: dev-b2g@lists.mozilla.org
 Sent: Monday, July 21, 2014 12:05:09 PM
 Subject: Re: [b2g] [Peak] device storage does not work properly

 the volume list looks like this:

  root@android:/ # vdc volume list
 
  110 sdcard /mnt/sdcard 4
 
  110 emmc /mnt/emmc 0
 
  110 fat /mnt/fat 0
 
  200 Volumes listed.
 

 As you thought, /system/etc/volume.cfg does not exist and
 /system/etc/vold.fstab contains this:

  dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.1/mmc_host
 

  dev_mount emmc /mnt/emmc 18 /devices/platform/msm_sdcc.3/mmc_host/mmc0
 

  dev_mount fat /mnt/fat auto /devices/virtual/block/loop7
 

 In addition I found this with adb logcat | grep Vold:

  I/Vold ( 126): Vold 2.1 (the revenge) firing up
 
  I/Vold ( 126): Load /etc/vold.origin.fstab. Do not use internal emmc
  partition.
 
  D/Vold ( 126): Volume sdcard state changing -1 (Initializing) - 0
  (No-Media)
 
  D/Vold ( 126): Volume emmc state changing -1 (Initializing) - 0 (No-Media)
 
  D/Vold ( 126): Volume fat state changing -1 (Initializing) - 0 (No-Media)
 
  D/Vold ( 126): Volume sdcard state changing 0 (No-Media) - 2 (Pending)
 
  D/Vold ( 126): Volume sdcard state changing 2 (Pending) - 1
  (Idle-Unmounted)
 
  D/VoldCmdListener( 126): volume list
 
  D/VoldCmdListener( 126): volume mount sdcard
 
  I/Vold ( 126): /dev/block/vold/179:33 being considered for volume sdcard
 
  D/Vold ( 126): Volume sdcard state changing 1 (Idle-Unmounted) - 3
  (Checking)
 
  W/Vold ( 126): Skipping fs checks
 
  I/Vold ( 126): Device /dev/block/vold/179:33, target /mnt/sdcard mounted @
  /mnt/secure/staging
 
  D/Vold ( 126): Volume sdcard state changing 3 (Checking) - 4 (Mounted)
 
  D/VoldCmdListener( 126): volume list
 

 -- Jovan

 2014-07-21 20:45 GMT+02:00 Dave Hylands  dhyla...@mozilla.com  :

  Hi Jovan,
 

  Device Storage gets its knowledge of which volumes exist from 2 sources.
 

  One is from the vold service. If you can get into an adb root shell (either
  use adb shell followed by su or adb root followed by adb shell) then you
  should be able to get vold's notion of volumes with this command:
 

  vdc volume list
 

  Device Storage also reads the /system/etc/volume.cfg file. I would expect
  this file to not be present on a geeksphone.
 

  If your vdc volume list looks wonky, then we can further investigate along
  those lines.
 
  vold determines its volumes by looking at /system/etc/vold.fstab (and I
  seem
  to recall older versions may have used another file as well, but I don't
  recall off the top of my head).
 

  Dave Hylands
 

   From: Jovan Gerodetti  titannanom...@gmail.com 
  
 
   To: dev-b2g@lists.mozilla.org
  
 
   Sent: Monday, July 21, 2014 11:02:47 AM
  
 
   Subject: [b2g] [Peak] device storage does not work properly
  
 

   Hi,
  
 

   While I experimented with my own builds and the official Geeksphone
   builds,
   I
   recognized that with an official build everything works fine but with my
   builds the device storage does not work as it should.
  
 

   1. The device detects no internal storage.
  
 
   2. In SettingsMedia Storage it displays Internal (actually my SD-Card)
   and
   two SD-Card slots even though the Peak has only one SD-Card slot.
  
 
   3. I have to select internal as default storage to be able to save files
   (with SD-Card I get requested to insert a SD-Card)
  
 
   3. The rescanning of the media apps does not work. If they have no
   indexDB
   they will find every file and after that they doesn't recognize any
   change...
  
 
   4. File browser apps take much longer to display the directory indexes.
  
 

   This all works with the official builds but not with my own builds. I
   experienced this problem since I create my own builds (since v1.4).
  
 
   Can someone think of anything how 

[b2g] Crash Reports for the week of 7/21/2014

2014-07-21 Thread Naoki Hirata
General news

mbrandt (Matt Brandt) will be joining as co-lead for 2.1 QA; please welcome him 
as the 2.1 co-lead.
Please set any crashes affecting Loop to block Meta: bug 1004761
New Feature Crashes

Loop

bug 1022058 - crash in 
sigslot::lock_blocksigslot::single_threaded::lock_block(sigslot::single_threaded*)
dev looked at; needs patch
bug 1009922 - [Open C] crash in __pthread_cond_pulse
dev looked atl needs patch
bug 1021451 - WebRTC Chat between FFOS and Desktop Computer Resulted in 
Graphics Crash - mozalloc_abort(char const*) | NS_DebugBreak | 
mozilla::ipc::FatalError(char const*, char const*, int, bool) | 
mozilla::layers::PSharedBufferManagerChild::SendAllocateGrallocBuffer
might be fixed by bug 1034294
2.1 : Gecko 33a1

bug 1035286 - crash in mozalloc_abort(char const*) | abort | 
js::jit::BacktrackingAllocator::splitAcrossCalls(js::jit::LiveInterval*)
bug 1035249 - crash in jemalloc_crash | arena_dalloc | je_free | free | 
js::detail::HashTableJS::Symbol* const, js::HashSetJS::Symbol*, 
js::HashSymbolsByDescription, js::SystemAllocPolicy::SetOps, 
js::SystemAllocPolicy::changeTableSize(int)
bug 1026631 - crash in jemalloc_crash | arena_salloc | je_realloc | realloc | 
moz_xrealloc | nsTArray_basensTArrayInfallibleAllocator, 
nsTArray_CopyWithMemutils::EnsureCapacity(unsigned int, unsigned int) | 
nsObserverList::AddObserver(nsIObserver*, bool)
bug 1026655 - crash in jemalloc_crash | arena_dalloc | je_free | free | 
moz_free | XPCNativeInterface::DestroyInstance(XPCNativeInterface*)
bug 1026672 - crash in jemalloc_crash | arena_dalloc | je_free | free | 
js::Shape::sweep()
2.0, the version formerly known as 1.5 : gecko 32a2

bug 1038461 - Failed to map ion memory in the client on gonk
bug 1038891 - OMXCodec crash while stability testing
bug 1036482 - Crash in low memory situation while stability testing
bug 1029710 - crash in mozilla::dom::ShadowRoot::IsPooledNode(nsIContent*, 
nsIContent*, nsIContent*)
bug 1026011 - crash in 
android::BpAudioPolicyService::initStreamVolume(audio_stream_type_t, int, int)
bug 1008791 - Crash in stability test [@ ? | pthread_kill | raise | 
__libc_android_abort | ... | js::BaseProxyHandler::get(JSContext*, JS::Handle, 
JS::Handle, JS::Handle, JS::MutableHandleJS::Value) ]___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g


[b2g] 07/21/2014 Flame 2.0 Smoke Test Results - 61/62 smoketests, 0 new blockers

2014-07-21 Thread Marcia Knous

* 39/39 automated smoketests passing

* 22/23 manual smoketests passing

* 0 reboots

* 0 crashes


Build Information

* Build ID: 20140721000201

* Version: 32.0a2

* Gecko: 4bd4b0ae7bbe

* Gaia: 8cb1a949f2e9650bb2c5598e78a6f24a58bbaf97

* Base Image: v122


New Bugs Breaking Manual Smoketests:

- None reported.


Existing Bugs Breaking Manual Smoketests:

- [B2G][OTA] Smart collections are not displayed after OTA 1.3 to 2.0

https://bugzilla.mozilla.org/show_bug.cgi?id=1037556

  **Resolved Fixed, blocked by bug 1040146

- [1.3 = 2.0] 2.0 tutorial is not displayed after an OTA update

https://bugzilla.mozilla.org/show_bug.cgi?id=1040146

- Modify APN for ATT because last update doesn't work as expected

https://bugzilla.mozilla.org/show_bug.cgi?id=1040700

  **Resolved Fixed, patch should be present in tomorrow's Smoke Test

- [B2G][OTA] The icon order within pages is not preserved when there are 
collections


https://bugzilla.mozilla.org/show_bug.cgi?id=1039968

  **Resolved Fixed, blocked by bug 1040146


New Bugs Breaking Automated Smoketests:

- None reported.


Existing Bugs Breaking Automated Smoketests:

- None reported.



Links

* Daily Smoketest Logs:

https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Zncusp=drive_web#gid=8https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Zncusp=drive_web#gid=8 
https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Zncusp=drive_web#gid=8


* MozTrap Results:

https://moztrap.mozilla.org/results/cases/?filter-run=4768

Sincerely,

Mozilla QA Team

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g


[b2g] 07/21/2014 Flame v2.1 Smoke Test Results - 38/49 tests passed, 2 new blockers

2014-07-21 Thread Marcia Knous
Note: Due to the fact that there was no Automation Report today, we ran 
a full smoketest today on this branch.


38 out of 49 tests passed for the 2014-07-21 Flame v2.1 Build. There are 
two new issues and one existing blocker that kept the smoketests from 
fully passing.



Smoketest Results:

Daily Smoke Test Logs:

https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Zncusp=drive_web#gid=0https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Zncusp=drive_web#gid=0 
https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Zncusp=drive_web#gid=0


Moztrap links:

Run:https://moztrap.mozilla.org/runtests/run/4766/env/347/

Results: 
https://moztrap.mozilla.org/results/cases/?filter-run=4766https://moztrap.mozilla.org/results/cases/?filter-run=4766



Tests Were Performed With:

Build ID: 20140721062116

Gecko: 0dc711216018

Gaia: N/A Gaia not available

Base Image: v122

OTA Updated From: 20140721000201 (2.0)

6 reboots

1 crash (New)


New Bugs Breaking the Smoketests:

- Modify APN for ATT because last update doesn't work as expected

https://bugzilla.mozilla.org/show_bug.cgi?id=1040700

  **Resolved Fixed, patch should be present in tomorrow's Smoketest
- [v2.1] Updating a contact causes the phone to restart
https://bugzilla.mozilla.org/show_bug.cgi?id=1041510

Existing Bugs Breaking the Smoketests:

- [B2G][SMS] User is unable to send an MMS
https://bugzilla.mozilla.org/show_bug.cgi?id=1040382
  **Resolved Fixed, patch should be included in tomorrow's Smoketest

New Issues Not Breaking the Smoketests:

- crash in 
mozilla::dom::exceptions::JSStackFrame::GetFilename(nsAString_internal)

https://bugzilla.mozilla.org/show_bug.cgi?id=1041646

Sincerely,

Mozilla QA Team

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g


[b2g] 7/21/2014 Flame 273MB v2.0 Smoke Test Results - 43/49 tests passed, 6 existing blockers

2014-07-21 Thread Marcia Knous
43 out of 49 tests passed for the 2014-07-21 Flame 273MB v2.0 Build. 
There are no new issues and six existing blockers that kept the 
smoketests from fully passing.



Smoketest Results:

Daily Smoke Test Logs:

https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Zncusp=drive_web#gid=10https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Zncusp=drive_web#gid=10 
https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Zncusp=drive_web#gid=10


Moztrap links:

Run:https://moztrap.mozilla.org/runtests/run/4772/env/347/

Results: 
https://moztrap.mozilla.org/results/cases/?filter-run=4772https://moztrap.mozilla.org/results/cases/?filter-run=4772



Tests Were Performed With:

Build ID: 20140721000201

Gecko: 4bd4b0ae7bbe

Gaia: 8cb1a949f2e9650bb2c5598e78a6f24a58bbaf97

Base Image: v122

OTA Updated From: v122 + 1.3 Gaia

1 reboot

0 crashes


New Bugs Breaking the Smoketests:

- None Reported


Existing Bugs Breaking the Smoketests:

- [B2G][OTA] Smart collections are not displayed after OTA 1.3 to 2.0
https://bugzilla.mozilla.org/show_bug.cgi?id=1037556
  **Resolved Fixed, blocked by bug 1040146
- [1.3 = 2.0] 2.0 tutorial is not displayed after an OTA update
https://bugzilla.mozilla.org/show_bug.cgi?id=1040146

- [B2G][OTA] The icon order within pages is not preserved when there are 
collections


https://bugzilla.mozilla.org/show_bug.cgi?id=1039968

  **Resolved Fixed, blocked by bug 1040146

- Modify APN for ATT because last update doesn't work as expected

https://bugzilla.mozilla.org/show_bug.cgi?id=1040700

  **Resolved Fixed, patch should be present in tomorrow's Smoke Test
- [B2G][SMS] User is unable to send an MMS
https://bugzilla.mozilla.org/show_bug.cgi?id=1040382

  **Resolved Fixed, patch should be present in tomorrow's Smoke Test

- Camera app receives sigkill after 15mins 480p recording in 256MB devices
https://bugzilla.mozilla.org/show_bug.cgi?id=1027592

New Issues Not Breaking the Smoketests:

- None Reported

Sincerely,

Mozilla QA Team

___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g


[b2g] mozilla-b2g32_v2_0 branch now live

2014-07-21 Thread Aki Sasaki
As of today's uplift, the Gecko side of B2G v2.0 now lives on the
mozilla-b2g32_v2_0 branch, *NOT* mozilla-aurora. Patches that are
blocking-b2g:2.0+ should be landed there now. For more information, see
the page below which always contains the latest information.
https://wiki.mozilla.org/Release_Management/B2G_Landing#v2.0.0

As a reminder, B2G v2.1 development remains on mozilla-central through
the duration of the Gecko 34 development cycle due to end on Sept 1, so
there is no change for where v2.1 patches are to land.
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g