Merge lp:~kdub/mir/fix-1577967 into lp:mir
| Status: | Merged |
|---|---|
| Approved by: | Kevin DuBois on 2016-06-08 |
| Approved revision: | 3509 |
| Merged at revision: | 3533 |
| Proposed branch: | lp:~kdub/mir/fix-1577967 |
| Merge into: | lp:mir |
| Diff against target: |
349 lines (+137/-48) 7 files modified
include/client/mir_toolkit/mir_surface.h (+17/-5) playground/mir_demo_client_prerendered_frames.c (+6/-0) src/client/mir_connection.cpp (+21/-25) src/client/mir_surface.cpp (+17/-16) src/client/mir_surface.h (+7/-2) tests/acceptance-tests/test_buffer_stream_arrangement.cpp (+45/-0) tests/unit-tests/client/test_client_mir_surface.cpp (+24/-0) |
| To merge this branch: | bzr merge lp:~kdub/mir/fix-1577967 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Mir CI Bot | continuous-integration | Approve on 2016-06-08 | |
| Daniel van Vugt | Abstain on 2016-06-08 | ||
| Cemil Azizoglu (community) | Approve on 2016-05-16 | ||
| Alan Griffiths | Approve on 2016-05-11 | ||
| Chris Halse Rogers | 2016-05-10 | Approve on 2016-05-11 | |
|
Review via email:
|
|||
Commit Message
fix lp: #1577967 by clarifying what mir_surface_
Description of the Change
fix lp: #1577967 by clarifying what mir_surface_
note: the original thought was designate the 1st MirBufferStream as 'the default stream', however, soon it will be possible to have multiple MirPresentation
| Chris Halse Rogers (raof) wrote : | # |
LGTM. Should we be marking all the mir_surface_* functions which implicitly deal with a default BufferStream as deprecated?
Certainly we should be marking mir_surface_
| Alan Griffiths (alan-griffiths) wrote : | # |
Triggered rebuild as a quick looks suggested extremely slow test hardware leading to timeouts.
~~~~
+ uint32_t output_id;
+
};
Unnecessary whitespace
| Mir CI Bot (mir-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:3505
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Kevin DuBois (kdub) wrote : | # |
> Certainly we should be marking mir_surface_
> deprecated. I lean towards marking mir_surface_
> deprecated, also, although there's not a direct replacement.
There is a way in the current API to work without mir_surface_
MirSurfaceSpec* spec = ...;
MirBufferStream* stream = mir_connection_
mir_surface_
MirSurface* surface = mir_surface_
now the client knows which stream is in the surface, and could change/swap as it wants to.
| Cemil Azizoglu (cemil-azizoglu) wrote : | # |
>LGTM. Should we be marking all the mir_surface_* functions which implicitly deal with a default >BufferStream as deprecated?
+1 as the names are really confusing.
Needs fixings :
153 + legacy_
Since the notion of "default stream" is not going away, we should just call it "default_stream".
-------
209 + auto resize_event = mir_event_
210 + size = { mir_resize_
211 + if (legacy_
212 + legacy_
The if statement should enclose the whole thing as it only makes sense when there is a default stream.
| Kevin DuBois (kdub) wrote : | # |
can add some deprecated tags to discourage use in the headers.
re legacy_
The size member variable is used in get_parameters, and should be changed when the resize event occurs.
| Mir CI Bot (mir-ci-bot) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
https:/
Executed test runs:
FAILURE: https:/
None: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
| Mir CI Bot (mir-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:3506
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Daniel van Vugt (vanvugt) wrote : | # |
A few failures:
16:48:22 9: [ FAILED ] 3 tests, listed below:
16:48:22 9: [ FAILED ] ServerStartup.
16:48:22 9: [ FAILED ] ServerStartup.
16:48:22 9: [ FAILED ] UnresponsiveCli
They are not pre-existing bugs or known failures...
| Daniel van Vugt (vanvugt) wrote : | # |
Just a reminder - the CI failures appear to be consistent and unique to this branch. So I guess the branch is faulty.
- 3507. By Kevin DuBois on 2016-05-20
-
merge in mir
- 3508. By Kevin DuBois on 2016-06-08
-
merge in mir
- 3509. By Kevin DuBois on 2016-06-08
-
remember to free spec in BufferStreamArr
angement test suite
| Mir CI Bot (mir-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:3508
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Kevin DuBois (kdub) wrote : | # |
CI was ran against rev3508... rev3509 has fix for valgrind+ci.
| Mir CI Bot (mir-ci-bot) wrote : | # |
PASSED: Continuous integration, rev:3509
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/

FAILED: Continuous integration, rev:3505 /mir-jenkins. ubuntu. com/job/ mir-ci/ 967/ /mir-jenkins. ubuntu. com/job/ build-mir/ 1041/console /mir-jenkins. ubuntu. com/job/ build-0- fetch/1088 /mir-jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= vivid+overlay/ 1079 /mir-jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= xenial/ 1079 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= clang,platform= mesa,release= vivid+overlay/ 1051/console /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= amd64,compiler= gcc,platform= mesa,release= xenial/ 1051/console /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= cross-armhf, compiler= gcc,platform= android, release= vivid+overlay/ 1051 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= cross-armhf, compiler= gcc,platform= android, release= vivid+overlay/ 1051/artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= i386,compiler= gcc,platform= android, release= vivid+overlay/ 1051 /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= i386,compiler= gcc,platform= android, release= vivid+overlay/ 1051/artifact/ output/ *zip*/output. zip /mir-jenkins. ubuntu. com/job/ build-2- binpkg- mir/arch= i386,compiler= gcc,platform= mesa,release= xenial/ 1051/console
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
ABORTED: https:/
Click here to trigger a rebuild: /mir-jenkins. ubuntu. com/job/ mir-ci/ 967/rebuild
https:/