Interop test with firefox for VP8, VP9 and H264 (instead of just default VP8).

Interop test with firefox for VP8, VP9 and H264 (instead of just default VP8).

The ?vsc=H264&vrc=H264 arguments seem to be ignored though (based on running
the tests locally and printf'ing in encoder/decoder).

BUG=

[hbos_chromium, 2016-05-25 13:31:18]

hbos@chromium.org changed reviewers:
+ phoglund@chromium.org

[hbos_chromium, 2016-05-25 13:31:19]

Here it is, feel free to scavenge. I'm not sure why the vsc/vrc arguments are
ignored because, but they are ignored and the fork being old could certainly
explain it. They are not ignored on https://apprtc.appspot.com/.

[phoglund_chromium, 2016-05-25 14:22:37]

looks good, but let's wait until you iron out the actual interop bugs.

[hbos_chromium, 2016-06-03 13:49:34]

Description was changed from

==========
Interop test with firefox for VP8, VP9 and H264 (instead of just default VP8).

The ?vsc=H264&vrc=H264 arguments seem to be ignored though (based on running
the tests locally and printf'ing in encoder/decoder). Maybe the apprtc version
is outdated?

BUG=
==========

to

==========
Interop test with firefox for VP8, VP9 and H264 (instead of just default VP8).

The ?vsc=H264&vrc=H264 arguments seem to be ignored though (based on running
the tests locally and printf'ing in encoder/decoder).

BUG=
==========

[hbos_chromium, 2016-06-03 13:49:46]

On 2016/05/25 14:22:37, phoglund_chrome wrote:
> looks good, but let's wait until you iron out the actual interop bugs.

Not sure if apprtc not working was a temporary problem or if I did something
wrong when I tested manually. ?vsc=H264&vrc=H264 does work manually now, but the
test of this CL does not. When running...

out/Release/browser_tests
--gtest_filter="WebRtcApprtcBrowserTest*FirefoxApprtcInteropTestH264"
--run-manual --ui-test-action-max-timeout=10000000

It uses VP8 as if vsc/vrc was not specified. I don't understand what is going
on, you being more familiar with this test, can you take a look phoglund?

[phoglund_chromium, 2016-06-09 07:21:56]

On 2016/06/03 13:49:46, hbos_chromium wrote:
> On 2016/05/25 14:22:37, phoglund_chrome wrote:
> > looks good, but let's wait until you iron out the actual interop bugs.
> 
> Not sure if apprtc not working was a temporary problem or if I did something
> wrong when I tested manually. ?vsc=H264&vrc=H264 does work manually now, but
the
> test of this CL does not. When running...
> 
> out/Release/browser_tests
> --gtest_filter="WebRtcApprtcBrowserTest*FirefoxApprtcInteropTestH264"
> --run-manual --ui-test-action-max-timeout=10000000
> 
> It uses VP8 as if vsc/vrc was not specified. I don't understand what is going
> on, you being more familiar with this test, can you take a look phoglund?

Could that our pinned version of AppRTC is too old. Can you re-run your test,
but don't connect to apprtc.appspot.com. From your chrome src dir, do this:

python ../google_appengine/dev_appserver.py ../apprtc/out/app_engine/

Then http://127.0.0.1:8080/ will have the same apprtc version the test is using.

Use the same browsers the test is using:

../firefox/firefox/firefox http://127.0.0.1:8080/r/test1?vsc=H264&vrc=H264
out/Default/chrome http://127.0.0.1:8080/r/test1?vsc=H264&vrc=H264

Let's see if that works first so we know how to proceed. I don't know how
to check if h264 was selected which is why I'm asking you (feel free to
come by my desk otherwise).

[hbos_chromium, 2016-06-10 09:25:47]

Update: Testing manually, interop works with VP8 and H264 but not VP9. With
browser_tests, neither VP9 or H264 works.

[hbos_chromium, 2016-06-10 09:26:48]

On 2016/06/10 09:25:47, hbos_chromium wrote:
> Update: Testing manually, interop works with VP8 and H264 but not VP9. With
> browser_tests, neither VP9 or H264 works.

And testing manually with two chrome tabs (no firefox) works with all codecs.