[b2g] 05/29/2014 TPE Hamachi Gaia UI Automation Master Mozilla RIL Build - 39/41 smoketests, 75/78 non-smoketests

Sorry, there will be no report today from Taipei QA. There are a few reasons. 1. The phone battery was totally dead even with the plug-in USB. The battery is not chargeable. 2. The phone crashed in a point that we don't know. I will put the phone with new battery back and see how it goes tomor

Re: [b2g] Please update the source code of Gecko and Gaia.

Thanks for reminder. One more thing need to clarify, if you use OLD gecko and NEW gaia will not break until Bug 1014487 is fixed. We will notice everyone in the mail list again. Thanks. Best regards - Gary Chen 陳柏宇 Mozilla Taiwan T: +886-2-87861100 # 206 M: +

[b2g] Please update the source code of Gecko and Gaia.

Hi All, Since the two preference names(browser.manifestURL and browser.homescreenURL) has been changed in bug 1013094 and the patch is already landed in mozilla central, the combination of the new gecko and old gaia will cause trouble. To avoid this, please keep your gecko and gaia both up to d

Re: [b2g] ZTE Open C

Hi Kobalt, Maybe you can do "make reset-gaia" in gaia folder also? If we move gecko to master branch, we should move gaia to master at same time. Thank you for your feedback and I think I should update it in bug 1016867 :) Here's my steps to make a clean build and I'm sure it works in my open C $

[b2g] 05/28/2014 Tarako v1.3 Smoke Test Results - 46/47 tests passed, no new blockers

46 out of 47 tests passed for the 2014-05-28 Tarako v1.3t Build. There is one existing issue that kept the smoketests from fully passing. Smoketest Results: Daily Smoke Test Logs: https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Znc&usp=drive_

Re: [b2g] Problem flashing gaia - ZTE Open C

Essentially, it seems to install a custom build of FFOS that unlocks the device to allow adb to connect to it. I tried adb before flashing and it just didn't recognise any devices. Apart from that, it would appear using this image disables automated updating from the Open C's built-in Software Upd

Re: [b2g] Problem flashing gaia - ZTE Open C

Does anyone know what this tool does? I can fastboot into the bootleader, and recovery, so if it can be installed from those modes, I could just do it directly. I was expecting a lot of rough edges and challenges from a new hacker OS, but I have to admit I was *not* expecting to be turned away bec

[b2g] 05/28/2014 Flame Master/M-C Smoke Test Results - 46/49 tests passed, no new blockers

46 out of 49 tests passed for the 2014-05-28 Flame Master M-C Build. There are two existing issues that kept the smoketests from fully passing. **Note: two Test Cases have been added to the 2.0 smoketest suite - OTA Update and Firefox Account Sign-in in Settings and Sign in to Persona TC has bee

[b2g] 05/28/2014 Flame v1.4 Smoke Test Results - 46/48 tests passed, no new blockers

46 out of 48 tests passed for the 2014-05-28 Flame v1.4.0 Build. There is one known Flame issue (bug 1008557 ) that kept the smoketests from fully passing. **Note: OTA update Test Case has been added to the smoketest suite and Sign in to Per

Re: [b2g] ZTE Open C

On Wednesday, May 28, 2014 5:00:02 AM UTC-5, Viral Wang wrote: > Hi, > > > > Actually Open C and flame should not used same code base. > > The reason that open C can use flame before is we use the build for msm8x10 > in the beginning. > > After that, we add some specific features like NFC in

[b2g] thread pointer for Firefox OS Gaia Email app and invalid certificates/certificate exceptions

In an attempt to address the cross-cutting https://bugzil.la/874346 on adding certificate exceptions initiated by the Firefox OS Gaia email app I've started a thread on dev.platform entitled "B2G, email, and SSL/TLS certificate exceptions for invalid certificates". If you're interested, please

Re: [b2g] 05/28/2014 Tarako 1.3 Smoke Test pending

Apologies, a build was just created a few moments ago; we will try to get a smoke test done today. Please ignore the previous message. On May 28, 2014, at 3:20 PM, Naoki Hirata wrote: > No Smoketest done for today's Tarako 1.3t build. > > There are several changeset that broke tarako builds s

[b2g] 05/28/2014 No Tarako 1.3 Smoke Test Report, no build

No Smoketest done for today's Tarako 1.3t build. There are several changeset that broke tarako builds so no 05/28 build is available: see bug https://bugzilla.mozilla.org/show_bug.cgi?id=1017073 for more info. Regards, Mozilla QA ___ dev-b2g mailing

[b2g] Flame 2.0 Test Run 1 - Start of 5/28/2014 Status

Current daily test run results for the latest Firefox OS 2.0 Full test run on Flame are below. 562 passed, 15 failed, 0 blocked, 27 invalid / 5055 cases total. Coverage is at 11.9%. Crashes: 0 Regressions: 2 Test Results: http://mzl.la/1tM8bOr Bugs: http://mzl.la/1tM92yw (all: 7) http://mzl.l

Re: [b2g] Building for ZTE Open C: "Failed to pull libnfc-nci.so. Giving up."

Thanks. I hope this means the Open C remains open enough to follow the Flame reference as closely as possible if that is the case. *-- Bitmessage me* *BM-2D97QV3Y4VRfjayrWahqE61XKuQw6dJvj6* On 28 May 2014 02:15, Антон Бородюк wrote: > On Wednesday, 28 May 2014 01:39:3

[b2g] 05/28/2014 Hamachi Gaia UI Automation v1.4 Mozilla RIL Build - 38/40 smoketests, 77/82 non-smoketests

Hi all, Here are todays Gaia automation results for v1.4. Cheers, Robert *Build under test:* Gaia cd595be0a8e975559e8938830df5face89bec3e8 Gecko https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/af180db8a4bf BuildID 20140528000201 Version 30.0 ro.build.version.i

Re: [b2g] ZTE Open C

So Open C users will pretty much end up without source code forever? Meh. "Open" platform is so open. Curse you ZTE. ___ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g

Re: [b2g] ZTE Open C

Hi, Actually Open C and flame should not used same code base. The reason that open C can use flame before is we use the build for msm8x10 in the beginning. After that, we add some specific features like NFC in flame. That's why some of errors happened if you only have open C in your hand. https:

Re: [b2g] Building for ZTE Open C: "Failed to pull libnfc-nci.so. Giving up."

On Wednesday, 28 May 2014 01:39:32 UTC+3, Rewarp wrote: > I am currently following the steps in the developer guides for building FFOS > from source. As per instruction, I am building them according to the "Flame" > reference device for the ZTE Open C. > > > > This is the error message I enco