Created attachment 83723 [details] [review] roster/groups: don't rely on an implementation detail Before telepathy-glib 0.20.3 and 0.21.1, we had this incorrect sequence (pseudocode) for each group: * NewChannels(the group) * GroupsChanged([the group], added: [...], removed: []) * NewChannels(the group) In 0.20.3 and 0.20.1, we removed the second emission of NewChannels (Bug #52011). Unfortunately, that broke this test, which was specifically expecting GroupsChanged followed by NewChannels. Rather than reversing the assumption, I'm doing it properly, by expecting the events in no particular order.
This is for 0.16 and 0.17. We should do a 0.18 new-stable branch soon.
Comment on attachment 83723 [details] [review] roster/groups: don't rely on an implementation detail Review of attachment 83723 [details] [review]: ----------------------------------------------------------------- ++
Fixed in git for 0.16.7 and 0.17.6 (or possibly 0.18.0)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.