Merge lp:~kdub/mir/buffer-stream-use-vault into lp:mir
| Status: | Merged |
|---|---|
| Approved by: | Kevin DuBois on 2015-08-28 |
| Approved revision: | 2842 |
| Merged at revision: | 2889 |
| Proposed branch: | lp:~kdub/mir/buffer-stream-use-vault |
| Merge into: | lp:mir |
| Prerequisite: | lp:~kdub/mir/client-stream-internal-refactoring |
| Diff against target: |
514 lines (+204/-39) 6 files modified
src/client/buffer_stream.cpp (+111/-2) src/client/buffer_vault.cpp (+7/-2) src/client/buffer_vault.h (+1/-1) tests/include/mir/test/doubles/null_client_buffer.h (+6/-1) tests/unit-tests/client/test_buffer_vault.cpp (+2/-2) tests/unit-tests/client/test_client_buffer_stream.cpp (+77/-31) |
| To merge this branch: | bzr merge lp:~kdub/mir/buffer-stream-use-vault |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Approve on 2015-08-28 | |
| Alexandros Frantzis (community) | Approve on 2015-08-27 | ||
| Alan Griffiths | Approve on 2015-08-27 | ||
| Chris Halse Rogers | 2015-08-20 | Needs Information on 2015-08-24 | |
|
Review via email:
|
|||
Commit Message
client: if not given a buffer at startup, switch to the new buffer semantics instead of throwing.
Description of the Change
client: if not given a buffer at startup, switch to the new buffer semantics instead of throwing.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2835
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
FAILURE: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Chris Halse Rogers (raof) wrote : | # |
28 + auto request = mcl::make_
Do we still need to do the heap-allocation dance? I *think* now that we can version libmirprotobuf we can safely use the stack?
Otherwise seems sensible.
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:2837
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Alexandros Frantzis (afrantzis) wrote : | # |
101 + return &next_buffer_
115 + MirWaitHandle next_buffer_
The default constructed MirWaitHandle will block if mir_wait_for_one() is invoked.
mir_wait_for_one is not particularly popular in our code base, but since we have it, we should ensure the wait handles we return work with it. Some paths in the ExchangeSemantics also have the same issue.
Looks good otherwise.
| Alan Griffiths (alan-griffiths) wrote : | # |
Alexandros has already spotted the only slight concern
| Kevin DuBois (kdub) wrote : | # |
Good point, fixed
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2840
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Autolanding.
More details in the following jenkins job:
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Autolanding.
Unapproved changes made after approval.
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
| Kevin DuBois (kdub) wrote : | # |
that will teach me to merge mir after top-approving...
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:2842
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://

FAILED: Continuous integration, rev:2834 jenkins. qa.ubuntu. com/job/ mir-ci/ 4633/ jenkins. qa.ubuntu. com/job/ mir-android- vivid-i386- build/3612 s-jenkins. ubuntu- ci:8080/ job/mir- clang-ts- vivid-amd64- build/33/ console jenkins. qa.ubuntu. com/job/ mir-clang- vivid-amd64- build/2523/ console jenkins. qa.ubuntu. com/job/ mir-mediumtests -vivid- touch/3562 jenkins. qa.ubuntu. com/job/ mir-wily- amd64-ci/ 782 jenkins. qa.ubuntu. com/job/ mir-wily- amd64-ci/ 782/artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ mir-mediumtests -builder- vivid-armhf/ 3562 jenkins. qa.ubuntu. com/job/ mir-mediumtests -builder- vivid-armhf/ 3562/artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ mir-mediumtests -runner- mako/6335 s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 22731
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/mir- ci/4633/ rebuild
http://