One messaging-app AP test failing with Qt 5.2

Bug #1291394 reported by Timo Jyrinki
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
messaging-app
Confirmed
Critical
Unassigned
messaging-app (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

As part of automated runs, one test was identified as failing with the messaging-app:

messaging_app.tests.test_messaging.TestMessaging.test_delete_multiple_messages(with touch)

This is when used together with Qt 5.2, which is about to land soon.

Upgrade instructions on the device:
adb shell
apt-add-repository ppa:ci-train-ppa-service/landing-006
apt-get update
apt-get dist-upgrade
# in case of lxc-android-config or other failures:
# dpkg --configure -a
reboot

Tags: qt5.2

Related branches

description: updated
Leo Arias (elopio)
Changed in messaging-app:
status: New → Confirmed
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

From Leo's e-mail:
"It doesn't affect the functionality of the app, as I can manually delete multiple messages. And if I add a sleep, the test will pass, so it's likely something that needs to be fixed on the test or on autopilot."

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package messaging-app - 0.1+14.04.20140314-0ubuntu1

---------------
messaging-app (0.1+14.04.20140314-0ubuntu1) trusty; urgency=low

  [ Leo Arias ]
  * Refactor the test_delete_multiple_messages to make it readable and
    maintainable.
  * Added a sleep to workaround an autopilot error we are getting with
    the qt5.2 landing PPA. (LP: #1291394)
 -- Ubuntu daily release <email address hidden> Fri, 14 Mar 2014 15:01:39 +0000

Changed in messaging-app (Ubuntu):
status: New → Fix Released
Changed in messaging-app:
status: Confirmed → Fix Released
Bill Filler (bfiller)
Changed in messaging-app:
status: Fix Released → Confirmed
Changed in messaging-app (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Leo Arias (elopio) wrote :

This bug is not fixed by the branch I made, it was just a quick and dirty workaround. We need to investigate more.

Revision history for this message
Leo Arias (elopio) wrote :

From boiko's branch:

After some more investigation, I found the real root cause of the problem. It happens because the messages on the thread used by the test are still unread, and then when you enter the view, the app requests history-service to mark them as read, which in turns triggers an update on the items, which makes the list view discard the previous delegates and create new ones.

I have changed the MR using the correct fix now, which is to only get the delegates after the items are already marked as read.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.