ubuntu-phone team mailing list archive

[Leo Arias <leo.arias@xxxxxxxxxxxxx>]

Hello,

On Fri, Jun 27, 2014 at 8:21 AM, Jussi Pakkanen <
jussi.pakkanen@xxxxxxxxxxxxx> wrote:

> Indeed. Here's an MR for that (it just disables the test):
>
> https://code.launchpad.net/~jpakkane/mediascanner2/
> sqliteworkaround/+merge/224845
>
> What this means in practice is that queries with only a few letters won't
> return results. Longer queries keep on working just like before. The proper
> fix is to dive into SQLite and see if the old behaviour can be re-enabled
> but that's a lot more work.


We don't want to have an artificial dashboard that's always green. If
something is broken, we want to know about it.

The current process allows for 7 days of known-issues before making it
critical to get a fix. It would be good to know if that extra work will
take more than 7 days. And even in that case, we can discuss about it,
maybe we could make it a known issue on a promoted image.

Also, the test-driven + continuous integration process works only if we
always keep the released features working. When there's a regression, it
should be considered the most critical thing to do next. So the idea is not
to land anything until the regression is fixed.

You will have a hard time convincing us about the need for removing this
test. But you should at least try. 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.

pura vida
-- 
¡paz y baile!
http://www.ubuntu.com