ubuntu-phone team mailing list archive

[Łukasz 'sil2100' Zemczak <lukasz.zemczak@xxxxxxxxxxxxx>]

Hi,

So, in overall I would also opt for getting the issue fixed instead of
just disabling the test, but I can understand the rationale for the
disablement itself; as this is an issue that's coming from a separate
component - and that the it's actually blocking landing of a serious
regression fix.

I agree with what the QA representatives said: let's disable the test
but only if we have a bug reported and at least having someone working
on it actively, making sure it gets actually fixed as soon as possible.
I would also encapsulate the actual test disablement in a big FIXME with
the bug number mentioned in the comments.

But as Steve already mentioned, let's get this bug escalated to the
sqlite3 upstream first.

Cheers.

On 27.06.2014 18:39, Julien Funk wrote:
> On Fri, Jun 27, 2014 at 12:10 PM, Leo Arias <leo.arias@xxxxxxxxxxxxx> wrote:
> 
> 
>>
>>  If we define a process for disabling tests, it should involve a bug
>> reported, triaged, critical, with a person assigned to it, and a comment
>> with QA's blessing.
>>
> 
> 
> +1
> 
> 
> 


-- 
Łukasz 'sil2100' Zemczak
 lukasz.zemczak@xxxxxxxxxxxxx
 www.canonical.com