lp://qastaging/~unity-team/qtmir/no-upstart-notification
- Get this branch:
- bzr branch lp://qastaging/~unity-team/qtmir/no-upstart-notification
Branch merges
- Gerry Boland (community): Disapprove
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
-
Diff: 30 lines (+0/-15)1 file modifiedsrc/platforms/mirserver/mirserverstatuslistener.cpp (+0/-15)
Related bugs
Bug #1374426: [ap] Dash sometimes fails to appear during Autopilot tests - causes fails | Critical | Fix Released |
Related blueprints
Branch information
Recent revisions
- 255. By Gerry Boland
-
Remove Upstart SIGSTOP signal notification on Mir server ready, unity8 already does it and at better time
- 253. By Gerry Boland
-
TaskController may call processStarted synchronously, so check for that in startApplication before adding Fixes: 1371047
Approved by: Michael Zanetti, PS Jenkins bot - 251. By Gerry Boland
-
Fix unstable test - be more careful about synchronizing the Qt image provider and Mir snapshot threads
Use a state boolean and locking to synchronise the threads only if necessary (inspired by QFuture design)
Approved by: Daniel d'Andrada, PS Jenkins bot - 249. By Daniel d'Andrada
-
MirSurfaceItem: Ensure all touch sequences sent to Mir surface are properly ended.
In order to have a testable MirSurfaceItem I had to mock qtmir::Session.
To mock qtmir::Session I had to define a qtmir::SessionInterfac e. That caused many s/Session/ SessionInterfac es throughout the code base.
When creating a testing::MockSession for qtmir::Session it clashed with the existing testing: :MockSession for mir::scene: :Surface. Thus I had to refactor the namespacing of all mocks. So most of the diff is just about refactoring code to enable a MirSurfaceItem unit test.
Fixes: 1295623
Approved by: Michael Zanetti, PS Jenkins bot
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://qastaging/qtmir