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.
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
13 matches
Mail list logo
