Hey list,
so I've been using Firefox OS on my Alcatel One Touch Fire since Nov
2013 as my only phone on a day-to-day basis. I'd like to share my
feedback to give you an impression about what I like and dislike about
it. I've been on branch 1.2 for pretty much the whole trip.
Gernerally when I
This is really interesting feedback; thanks Johannes! I can only really speak
for the documentation aspect of the project, so the comments below will only
focus on those. I’ll let other better qualified team members comment on the dev
process issues, etc.
One thing I will say is that the OS is
+1 @ root cause analysis
I assumed this was the cause of the error, I started seeing it at the same
time, but does anyone know what is up with
https://bugzilla.mozilla.org/show_bug.cgi?id=1019552 ? I flashed master
today and the homescreen is fixed for me, but this still shows up
On 3 June 2014
Hey Chris,
On 03.06.2014 13:00, Chris Mills wrote:
This is really interesting feedback; thanks Johannes! I can only really speak
for the documentation aspect of the project, so the comments below will only
focus on those. I’ll let other better qualified team members comment on the
dev
On 6/3/2014 8:18 AM, Johannes Bauer wrote:
Reading through my message again, it's clear that I really hit the wrong
tone. I sound all bitchy and pissed which is not what I wanted to come
across as. Thanks for ignoring that attitude and focusing on the content.
FWIW, brutally honest feedback is
If it's any consolation I'm a staff member and my dogfooding bugs get
ignored, too :)
I recall that dialing bug - I am pretty sure we fixed that. It
definitely doesn't exist in 2.0.
As Chris said, v2.0 is light years ahead of v1.2.
Thanks for giving it a go anyway, you've given it far more
On 3/6/2014, 8:18, Johannes Bauer wrote:
One problem for me is that I cannot tell which components are
proprietary (vendor-specific) and which aren't. During the build process
the phone has to be hooked up so it can fetch these proprietary files.
It's not transparent to me where these files end
Hi Everyone,
The smoketest regression rate on trunk is out of control right now. We have
such problems as:
1. The dialer is entirely broken right now - can't make phone calls, call log
is suspected to be broken, inbound call icons are gone in the call log
** bug 1018474, bug 1019607, bug
Have we backed out all the regressing patches?
Andreas
On Jun 3, 2014, at 8:13 AM, Jason Smith jsm...@mozilla.com wrote:
Hi Everyone,
The smoketest regression rate on trunk is out of control right now. We have
such problems as:
1. The dialer is entirely broken right now - can't make
Having a tree closure in the last week to FL is super painful. It certainly
adds a lot of risk to the vertical homescreen and other features.
What is the criteria to get the tree re-opened? Is it resolving all of the
mentioned bugs?
Best,
Kevin
- Original Message -
From: Anthony
Kevin Grandon schrieb:
Having a tree closure in the last week to FL is super painful.
Yes, it is.
Landing patches that break usage of builds is even more painful though.
AFAIK, we want people to be able to test Nightly/master on their
devices. Considering that, things not being able to make
Ok, and that's all I was looking for :) When there is a tree closure it would
be nice to see what exactly needs to be done and who is looking at it so other
folks can jump in as needed.
Best,
Kevin
- Original Message -
From: Anthony Ricaud anth...@ricaud.me
To:
(answering on dev-b2g only, crossposting is painful)
Le 03/06/2014 17:53, L. David Baron a écrit :
On Tuesday 2014-06-03 08:13 -0700, Jason Smith wrote:
I need this under control as soon as possible, as these regressions are causing
the build to move towards being completely not functional.
Hi all,
Here is the first Flame Gaia UI tests v2.0 automation report.
We still have some issues to fix to make it bullet proof and we are
working on them.
Looks like the Dialer app is Broken the rest of the issues are because
of the Gaia-Ui- test
Cheers,
Bebe.
*Build under test:*
Le 03/06/2014 18:24, Dave Hylands a écrit :
Do we even have tests which run on a real device?
We have some but they're not running on each commit, rather every day.
There is an effort to have a fake RIL daemon so that we can simulate the
network in the lowest level and experience all the
Do we even have tests which run on a real device?
If not, how can we write a test to verify that a call can be made?
Dave Hylands
- Original Message -
From: Julien Wajsberg jwajsb...@mozilla.com
To: dev-b2g dev-b2g@lists.mozilla.org
Sent: Tuesday, June 3, 2014 9:05:22 AM
Tree is reopened. I backed out bug 987487 to fix bug 1019639, bug
1019205 and bug 1019607. Jason confirmed on IRC that he is ok not
waiting for bug 1019228 to be fixed.
Sorry for not outlining the steps to re-open the tree, I haven't closed
the tree in a while and was a bit rusty on the exact
Yes we have the tests and they are run regularly.
The device test caught the dialer bug, but only on the twice daily
releng builds which is a rough range.
We couldn't catch it on the m-c tinderbox.ui builds because of the bug
that hamachi builds were too large for the device and thus the
On 03/06/2014 18:28, Julien Wajsberg wrote:
Le 03/06/2014 18:24, Dave Hylands a écrit :
Do we even have tests which run on a real device?
We have some but they're not running on each commit, rather every day.
There is an effort to have a fake RIL daemon so that we can simulate the
What about the consistent travis failure
test_persona_app.py
test_persona_app.TestPersonaStandard.test_persona_standard_sign_in
looks like it started with
https://github.com/mozilla-b2g/gaia/commit/4d3d20bee8d776278a48f6fd01c928e57e96b626
which doesnt look like the culprit, so a newly picked up
Here is the report from that test run*
http://mozilla-releng-travis-uploads.s3.amazonaws.com/artifacts/43525/43525.4/gaia_ui_tests_report.html
You can see that something has gone bad initializing Persona. The test
has timed out where it hasn't started up properly.
I've got to go now but see
There are two pieces here. The first piece is that the tests for the
feature were not as complete as they might have been, you can see that
in the bug. Andrea jumped in and fixed that, which is great.
The most solid way to provide CI for this is to run a sanity test on
Flame devices per
Hi all,
There have been a couple of threads related to test automation in B2G,
asking why we haven't caught some especially egregious regressions; the
kind that basically break the phone.
To answer that, I'd like to describe how our on-device automation
currently works, and what we're doing
I should have noted that the existing on-device automation did catch the
issue, but due to the wide range between device runs[1] the bug was
filed before the investigation work to find the issue was completed.
Clint
[1] The 12 phones in automation right now run both UI and performance
tests.
All,
Some upstream repositories changed in non-fast-forward manner, and the
automation does not push those changes to our mirrors (as designed).
Per the discussion in bug 1017623 we manually took changes to these 4
repositories. Depending where and how you clone, you may see error
messages from
ZTE are releasing a Android variant of the Open C, the Kis 3.
if anyone wants the kernel source it's here:
http://download.ztedevices.com/uploadfiles/copyright/mobilephones/ZTE_V811/ZTE_V811.KK.34x.kernel.tar.gz
___
dev-b2g mailing list
48 out of 48 tests passed for the 2014-06-03 Flame v1.4.0 Build. There
are no major issues preventing smoketest from passing.
Smoketest Results:
Daily Smoke Test Logs:
https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Zncusp=drive_web#gid=6
Hello all,
There was no Master/M-C smoke test done today due to multiple blocking
issues in today's build. Please note, bug 987487 has been backed out and
most of the issues should be fixed in tomorrow's build.
Existing Bugs Breaking the Smoketests:
- [B2G][Dialer] Inbound call icon missing
47 out of 47 tests passed for the 2014-06-03 Tarako v1.3t Build. There are no
major issues preventing smoketest from passing.
Smoketest Results:
Daily Smoke Test Logs:
https://docs.google.com/a/qanalydocs.com/spreadsheet/ccc?key=0AjRc6aVFoOW9dGZLdVdiWGZLbVdORlFpUGt5XzZ3Zncusp=drive_web#gid=5
Hi,
I have a Flame which I've been using as my day-to-day phone for the
past week or so.
The battery life is terrible. I'm a very light user -- just a couple
of calls and/or texts per day -- and I'm having to charge it every
day. My old Keon used to last a week between charges.
For example,
On Tue, Jun 3, 2014 at 6:47 PM, Nicholas Nethercote
n.netherc...@gmail.com wrote:
Hi,
I have a Flame which I've been using as my day-to-day phone for the
past week or so.
The battery life is terrible. I'm a very light user -- just a couple
of calls and/or texts per day -- and I'm having to
On Tue, Jun 3, 2014 at 6:50 PM, Kyle Huey m...@kylehuey.com wrote:
I'm quite surprised that the Flame has kernel shared memory turned on.
AFAIK ksm stands for kernel samepage merging but I bet we're
talking about the same thing.
Nick
___
dev-b2g
Hi,
sometimes when testing, we might need to record a screencast of what is
happening on the screen. Is there a way to get the video output of the screen
on Firefox OS? Is there a way to record it?
Is there a bug about it? I didn't find anything relevant.
I have used: http://droid-at-screen.ribomation.com/ Not exactly fast though.
I usually just use screenflow with the simulator.
- Original Message -
From: Karl Dubost kdub...@mozilla.com
To: dev-b2g@lists.mozilla.org
Sent: Tuesday, June 3, 2014 7:16:15 PM
Subject: [b2g] Recording the
34 matches
Mail list logo
