webrtc_client_test failed on GM8136 (ARM) about amazon-kinesis-video-streams-webrtc-sdk-c HOT 13 CLOSED

Log of running kvsWebrtcClientMaster and kvsWebrtcClientViewer,
I don't think that worked. Any idea?

kvsWebrtcClientMaster.log
kvsWebrtcClientViewer.log

from amazon-kinesis-video-streams-webrtc-sdk-c.

Hi @hsinghaowang. Sorry I was on vacation this week, when I get back into the office I will look right away!

It looks like TURN failed, can you try disabling it here you can pass false for useTurn

If the GM8136 device and the other peer are in the same subnet it should be able to connect without TURN. We will work on investigating the TURN connection issue.

Are you able to symbolize that segfault? I would make sure you are using the latest (and you have update the git submodule), we did fix some bugs in our dependencies.

I really appreciate you trying out the asset :) if there is anything we can improve/change I would love to hear. We are really excited see what people are building. thanks!

from amazon-kinesis-video-streams-webrtc-sdk-c.

After TURN is disabled, the log looks OK now.
BTW, I ran the master & viewer at the same device.

kvsWebrtcClientMaster2.log
kvsWebrtcClientViewer2.log

from amazon-kinesis-video-streams-webrtc-sdk-c.

I pulled the latest code. The webrtc_client_test log is:
webrtc_client_test3.log

It ran over 90 minutes and still not ended.

found one failure:

../../tst/PeerConnectionFunctionalityTest.cpp:101: Failure
Expected equality of these values:
  connectTwoPeers(offerPc, answerPc)
    Which is: false

from amazon-kinesis-video-streams-webrtc-sdk-c.

@hsinghaowang The test suite should complete in ~5 minutes.

Do you know what tests are taking the longest? We should add timeouts to those ones.

from amazon-kinesis-video-streams-webrtc-sdk-c.

according to webrtc_client_test3.log, the last test is
PeerConnectionFunctionalityTest.connectTwoPeersForcedTURN

from amazon-kinesis-video-streams-webrtc-sdk-c.

Nice! Sorry missed that @hsinghaowang

I will work on fixing TURN with ARMv5, thank you for reporting! We haven't added ARM testers to travis yet, so hard to catch that regressions

from amazon-kinesis-video-streams-webrtc-sdk-c.

@hsinghaowang Sorry for the delay, this will be fixed by Friday or Monday at the latest . If you have issues in the future I will make sure they get fixed away. Schedules were just pushed back a bit by the holidays.

Thanks for the patience!

from amazon-kinesis-video-streams-webrtc-sdk-c.

Hey @hsinghaowang

I was able to cross-compile and deploy to the device, unfortunately PeerConnectionFunctionalityTest.connectTwoPeersForcedTURN passes for me.

from amazon-kinesis-video-streams-webrtc-sdk-c.

It does surprise me how long it hangs on the following operations

2020-01-11 08:52:47 VERBOSE signalingClientGetIceConfigInfo(): Signaling Client Get ICE Config Info

and

Ice agent state changed from ICE_AGENT_STATE_NONE to ICE_AGENT_STATE_NEW.

I am going to see if I find a way to speed these up. Thanks!

from amazon-kinesis-video-streams-webrtc-sdk-c.

I am running amazon-kinesis-video-streams-webrtc-sdk-c @ 0a6103f550f6132557a39dc7764e8941c43c0a5e

from amazon-kinesis-video-streams-webrtc-sdk-c.

Thanks for your help.

from amazon-kinesis-video-streams-webrtc-sdk-c.

@hsinghaowang Did updating to that SHA1 fix things for you, if so fantastic news! Sorry for the bugs, and appreciate the reports :)

from amazon-kinesis-video-streams-webrtc-sdk-c.