Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(245)

Issue 2909073002: Enable webrtc_nonparallel_tests on iOS simulator (Closed)

Created:
3 years, 6 months ago by kjellander_webrtc
Modified:
3 years, 6 months ago
CC:
webrtc-reviews_webrtc.org, tterriberry_mozilla.com, kwiberg-webrtc
Target Ref:
refs/heads/master
Project:
webrtc
Visibility:
Public.

Description

Enable webrtc_nonparallel_tests on iOS simulator After landing https://chromium-review.googlesource.com/528173 only one test needs to be disabled: VirtualSocketServerTest.delay_v4 BUG=webrtc:7727 NOTRY=True TESTED=gn gen out/x64-Debug --args='target_os="ios" ios_enable_code_signing=false is_component_build=false target_cpu="x64"' ninja -C out/x64-Debug webrtc_nonparallel_tests out/x64-Debug/iossim -d "iPhone 6s" -s 10.3 out/x64-Debug/webrtc_nonparallel_tests.app Review-Url: https://codereview.webrtc.org/2909073002 Cr-Commit-Position: refs/heads/master@{#18519} Committed: https://chromium.googlesource.com/external/webrtc/+/c131bf944e939131a04753bf7c6ec06b56378024

Patch Set 1 : Disabling tests #

Patch Set 2 : Disable more tests #

Patch Set 3 : Remove test disablings #

Patch Set 4 : Disable only VirtualSocketServerTest.delay_v4 #

Patch Set 5 : Updated comment #

Patch Set 6 : Updated comment agaiin #

Unified diffs Side-by-side diffs Delta from patch set Stats (+12 lines, -1 line) Patch
M tools_webrtc/ios/tests/common_tests.json View 1 chunk +3 lines, -0 lines 0 comments Download
M webrtc/base/virtualsocket_unittest.cc View 1 2 3 4 5 1 chunk +9 lines, -1 line 0 comments Download

Messages

Total messages: 28 (17 generated)
kjellander_webrtc
Taylor, let me know if there's a nicer way to do this. The sockets seems ...
3 years, 6 months ago (2017-05-30 11:58:21 UTC) #11
Taylor Brandstetter
On 2017/05/30 11:58:21, kjellander_webrtc wrote: > Taylor, let me know if there's a nicer way ...
3 years, 6 months ago (2017-05-31 06:54:55 UTC) #12
kjellander_webrtc
On 2017/05/31 06:54:55, Taylor Brandstetter wrote: > On 2017/05/30 11:58:21, kjellander_webrtc wrote: > > Taylor, ...
3 years, 6 months ago (2017-05-31 08:14:10 UTC) #13
kjellander_webrtc
+oprypin
3 years, 6 months ago (2017-05-31 08:22:32 UTC) #14
oprypin_webrtc
On 2017/05/31 06:54:55, Taylor Brandstetter wrote: > On 2017/05/30 11:58:21, kjellander_webrtc wrote: > > Taylor, ...
3 years, 6 months ago (2017-06-01 16:46:38 UTC) #15
kjellander_webrtc
PTAL, I updated this after https://chromium-review.googlesource.com/528173 was landed and it looks promising! The VirtualSocketServerTest.delay_v4 test ...
3 years, 6 months ago (2017-06-09 12:16:00 UTC) #19
Taylor Brandstetter
lgtm. delay_v4 is a test that seems unsafe to run on a simulator in the ...
3 years, 6 months ago (2017-06-09 18:39:58 UTC) #20
kjellander_webrtc
On 2017/06/09 18:39:58, Taylor Brandstetter wrote: > lgtm. delay_v4 is a test that seems unsafe ...
3 years, 6 months ago (2017-06-09 19:56:40 UTC) #21
commit-bot: I haz the power
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/2909073002/180001
3 years, 6 months ago (2017-06-09 19:56:57 UTC) #24
commit-bot: I haz the power
Committed patchset #6 (id:180001) as https://chromium.googlesource.com/external/webrtc/+/c131bf944e939131a04753bf7c6ec06b56378024
3 years, 6 months ago (2017-06-09 19:59:18 UTC) #27
Taylor Brandstetter
3 years, 6 months ago (2017-06-09 22:22:31 UTC) #28
Message was sent while issue was closed.
On 2017/06/09 19:56:40, kjellander_webrtc wrote:
> On 2017/06/09 18:39:58, Taylor Brandstetter wrote:
> > lgtm. delay_v4 is a test that seems unsafe to run on a simulator in the
first
> > place; it relies on being able to process packets fast enough in real time.
> 
> Alright. I updated the comment with that and won't reference the bug (which
can
> then be closed).
> It makes me think the test belongs in webrtc_perf_tests though, not being a
> correctness test after all.

I think it should be rewritten to use the fake clock, actually. It's not trying
to test performance per se, it's just testing the "transit delay distribution"
feature of VirtualSocketServer, and sends a bunch of packets over time to do so.
I'll make a Cl since it should be trivial.

Powered by Google App Engine
This is Rietveld 408576698