|
|
DescriptionSkip unit test if GYP_DEFINES="rtc_use_h264=1" is not set.
Unit test would fail in default configuration (e.g. rtc_use_h264=0), cause it tests instantiating H264 specifics.
BUG=webrtc:6194, webrtc:6198
Committed: https://crrev.com/073ece45b68fc1aecb88692438bcb762e9fd18d5
Cr-Commit-Position: refs/heads/master@{#13929}
Patch Set 1 #Patch Set 2 : add #define to gyp and gn #
Messages
Total messages: 29 (15 generated)
johan@webrtc.org changed reviewers: + mflodman@webrtc.org
Update: no review needed right now. Patch Set 1 will not work if rtc_use_h264=1 is set, as define WEBRTC_USE_H264 will be set only in ./modules/video_coding/codecs/h264/h264.gypi:29 which does not affect webrtc/media/engine/webrtcvideoengine2_unittest.cc .
The CQ bit was checked by johan@webrtc.org 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.webrtc.org/...
mflodman, please have a look
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: android_arm64_rel on master.tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_dbg on master.tryserver.webrtc (JOB_TIMED_OUT, no build URL)
Description was changed from ========== Skip unit test if GYP_DEFINES="rtc_use_h264=1" is not set. BUG=webrtc:6194 ========== to ========== Skip unit test if GYP_DEFINES="rtc_use_h264=1" is not set. BUG=webrtc:6194, webrtc:6198 ==========
Description was changed from ========== Skip unit test if GYP_DEFINES="rtc_use_h264=1" is not set. BUG=webrtc:6194, webrtc:6198 ========== to ========== Skip unit test if GYP_DEFINES="rtc_use_h264=1" is not set. Unit test would fail in default configuration (e.g. rtc_use_h264=0), cause it tests instantiating H264 specifics. BUG=webrtc:6194, webrtc:6198 ==========
On 2016/08/09 13:42:24, johan wrote: > mflodman, please have a look ping
sprang@webrtc.org changed reviewers: + magjed@webrtc.org, sprang@webrtc.org - mflodman@webrtc.org
-mflodman +magjed magjed ptal, you probably have more time for reviews than mflodman right now?
lgtm
The CQ bit was checked by johan@webrtc.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_arm64_rel on master.tryserver.webrtc (JOB_TIMED_OUT, no build URL) android_dbg on master.tryserver.webrtc (JOB_TIMED_OUT, no build URL)
The CQ bit was checked by johan@webrtc.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_rel on master.tryserver.webrtc (JOB_FAILED, http://build.chromium.org/p/tryserver.webrtc/builders/android_rel/builds/15836)
The CQ bit was checked by johan@webrtc.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...
Message was sent while issue was closed.
Description was changed from ========== Skip unit test if GYP_DEFINES="rtc_use_h264=1" is not set. Unit test would fail in default configuration (e.g. rtc_use_h264=0), cause it tests instantiating H264 specifics. BUG=webrtc:6194, webrtc:6198 ========== to ========== Skip unit test if GYP_DEFINES="rtc_use_h264=1" is not set. Unit test would fail in default configuration (e.g. rtc_use_h264=0), cause it tests instantiating H264 specifics. BUG=webrtc:6194, webrtc:6198 ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== Skip unit test if GYP_DEFINES="rtc_use_h264=1" is not set. Unit test would fail in default configuration (e.g. rtc_use_h264=0), cause it tests instantiating H264 specifics. BUG=webrtc:6194, webrtc:6198 ========== to ========== Skip unit test if GYP_DEFINES="rtc_use_h264=1" is not set. Unit test would fail in default configuration (e.g. rtc_use_h264=0), cause it tests instantiating H264 specifics. BUG=webrtc:6194, webrtc:6198 Committed: https://crrev.com/073ece45b68fc1aecb88692438bcb762e9fd18d5 Cr-Commit-Position: refs/heads/master@{#13929} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/073ece45b68fc1aecb88692438bcb762e9fd18d5 Cr-Commit-Position: refs/heads/master@{#13929}
Message was sent while issue was closed.
On 2016/08/26 10:00:03, commit-bot: I haz the power wrote: > Patchset 2 (id:??) landed as > https://crrev.com/073ece45b68fc1aecb88692438bcb762e9fd18d5 > Cr-Commit-Position: refs/heads/master@{#13929} Sorry about this, we've been wanting to setup a bot (https://bugs.chromium.org/p/chromium/issues/detail?id=606944) for this config but it's been slipping due to higher prio tasks. |