|
|
DescriptionChange unique_ptr::reset() for std::move
BUG=644626
Committed: https://crrev.com/8e7155967dd6101ffb529c76005c7cccc75c26c8
Cr-Commit-Position: refs/heads/master@{#418616}
Patch Set 1 #Patch Set 2 : Change linked_ptr to unique_ptr #
Total comments: 1
Patch Set 3 : Change unique_ptr::reset() for std::move #
Messages
Total messages: 32 (19 generated)
The CQ bit was checked by brusi_roy@hotmail.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: No L-G-T-M from a valid reviewer yet. CQ run can only be started by full committers or once the patch has received an L-G-T-M from a full committer. Even if an L-G-T-M may have been provided, it was from a non-committer, _not_ a full super star committer. See http://www.chromium.org/getting-involved/become-a-committer Note that this has nothing to do with OWNERS files.
Description was changed from ========== Change unique_ptr::reset() for std::move BUG=644626 ========== to ========== Change unique_ptr::reset() for std::move BUG=644626 ==========
brusi_roy@hotmail.com changed reviewers: + sandersd@chromium.org, thestig@chromium.org
lgtm
The CQ bit was checked by brusi_roy@hotmail.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromeos_x86-generic_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_x86-ge...)
The CQ bit was checked by brusi_roy@hotmail.com
The patchset sent to the CQ was uploaded after l-g-t-m from sandersd@chromium.org Link to the patchset: https://codereview.chromium.org/2330543002/#ps20001 (title: "Change linked_ptr to unique_ptr")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromeos_x86-generic_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_x86-ge...)
https://codereview.chromium.org/2330543002/diff/20001/media/gpu/v4l2_video_de... File media/gpu/v4l2_video_decode_accelerator.cc (right): https://codereview.chromium.org/2330543002/diff/20001/media/gpu/v4l2_video_de... media/gpu/v4l2_video_decode_accelerator.cc:651: std::unique_ptr<BitstreamBufferRef>& buffer_ref = This change does not make sense to me, since the queue is of linked_ptrs.
The CQ bit was checked by brusi_roy@hotmail.com to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
On 2016/09/13 18:30:59, sandersd wrote: > This change does not make sense to me, since the queue is of linked_ptrs. You are right! I don't know how I missed that. Also, thank you for bearing with me, this is my first patch so I'm having a bit of trouble. Lastly, a newbie question if you have time: Is it normal that when I modify a file in src/media/... and then run `ninja -C out/Default chrome` I get "no work to do."? Is it because this file is not use on my platform? Thank you.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
On 2016/09/14 01:06:47, Brusi wrote: > On 2016/09/13 18:30:59, sandersd wrote: > > > This change does not make sense to me, since the queue is of linked_ptrs. > > You are right! I don't know how I missed that. Also, thank you for bearing with > me, this is my first patch so I'm having a bit of trouble. > Lastly, a newbie question if you have time: Is it normal that when I modify a > file in src/media/... and then run `ninja -C out/Default chrome` I get "no work > to do."? Is it because this file is not use on my platform? > > Thank you. This is the expected result, if indeed the file is not in use on your platform. You can check with the gn refs command: gn refs <out dir> //<file path> --all For example, with a Linux target: $ gn refs out/Debug //media/base/video_frame.cc --all | grep chrome$ //chrome:chrome $ $ gn refs out/Debug //media/base/gpu/vaapi_video_decode_accelerator.cc --all | grep chrome$ $
On 2016/09/14 17:45:16, sandersd wrote: > On 2016/09/14 01:06:47, Brusi wrote: > > On 2016/09/13 18:30:59, sandersd wrote: > > > > > This change does not make sense to me, since the queue is of linked_ptrs. > > > > You are right! I don't know how I missed that. Also, thank you for bearing > with > > me, this is my first patch so I'm having a bit of trouble. > > Lastly, a newbie question if you have time: Is it normal that when I modify a > > file in src/media/... and then run `ninja -C out/Default chrome` I get "no > work > > to do."? Is it because this file is not use on my platform? > > > > Thank you. > > This is the expected result, if indeed the file is not in use on your platform. > > You can check with the gn refs command: > gn refs <out dir> //<file path> --all > > For example, with a Linux target: > $ gn refs out/Debug //media/base/video_frame.cc --all | grep chrome$ > //chrome:chrome > $ > > $ gn refs out/Debug //media/base/gpu/vaapi_video_decode_accelerator.cc --all | > grep chrome$ > $ OK! thanks I will look into it! Is this patch ready to be committed?
On 2016/09/14 17:50:05, Brusi wrote: > On 2016/09/14 17:45:16, sandersd wrote: > > On 2016/09/14 01:06:47, Brusi wrote: > > > On 2016/09/13 18:30:59, sandersd wrote: > > > > > > > This change does not make sense to me, since the queue is of linked_ptrs. > > > > > > You are right! I don't know how I missed that. Also, thank you for bearing > > with > > > me, this is my first patch so I'm having a bit of trouble. > > > Lastly, a newbie question if you have time: Is it normal that when I modify > a > > > file in src/media/... and then run `ninja -C out/Default chrome` I get "no > > work > > > to do."? Is it because this file is not use on my platform? > > > > > > Thank you. > > > > This is the expected result, if indeed the file is not in use on your > platform. > > > > You can check with the gn refs command: > > gn refs <out dir> //<file path> --all > > > > For example, with a Linux target: > > $ gn refs out/Debug //media/base/video_frame.cc --all | grep chrome$ > > //chrome:chrome > > $ > > > > $ gn refs out/Debug //media/base/gpu/vaapi_video_decode_accelerator.cc --all > | > > grep chrome$ > > $ > > OK! thanks I will look into it! Is this patch ready to be committed? I believe so. With straightforward changes like these we have pretty good faith in the tests :-).
The CQ bit was checked by brusi_roy@hotmail.com
The patchset sent to the CQ was uploaded after l-g-t-m from sandersd@chromium.org Link to the patchset: https://codereview.chromium.org/2330543002/#ps40001 (title: "Change unique_ptr::reset() for std::move")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Change unique_ptr::reset() for std::move BUG=644626 ========== to ========== Change unique_ptr::reset() for std::move BUG=644626 ==========
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== Change unique_ptr::reset() for std::move BUG=644626 ========== to ========== Change unique_ptr::reset() for std::move BUG=644626 Committed: https://crrev.com/8e7155967dd6101ffb529c76005c7cccc75c26c8 Cr-Commit-Position: refs/heads/master@{#418616} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/8e7155967dd6101ffb529c76005c7cccc75c26c8 Cr-Commit-Position: refs/heads/master@{#418616} |