Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webrtc_client_test failed on GM8136 (ARM) #98

Closed
hsinghaowang opened this issue Dec 25, 2019 · 13 comments
Closed

webrtc_client_test failed on GM8136 (ARM) #98

hsinghaowang opened this issue Dec 25, 2019 · 13 comments

Comments

@hsinghaowang
Copy link

Here is the webrtc_client_test log running on our platform:
webrtc_client_test.log

CPU: GM8136 (armv5)
RAM: 128MB
OS: arm-linux-3.3
compiler: clang 9

@hsinghaowang
Copy link
Author

hsinghaowang commented Dec 25, 2019

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

kvsWebrtcClientMaster.log
kvsWebrtcClientViewer.log

@Sean-Der
Copy link
Contributor

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!

@hsinghaowang
Copy link
Author

hsinghaowang commented Dec 27, 2019

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

kvsWebrtcClientMaster2.log
kvsWebrtcClientViewer2.log

@hsinghaowang
Copy link
Author

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

@Sean-Der
Copy link
Contributor

@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.

@hsinghaowang
Copy link
Author

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

@Sean-Der
Copy link
Contributor

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

@Sean-Der
Copy link
Contributor

Sean-Der commented Jan 7, 2020

@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!

@Sean-Der
Copy link
Contributor

Hey @hsinghaowang

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

@Sean-Der
Copy link
Contributor

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!

@Sean-Der
Copy link
Contributor

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

@hsinghaowang
Copy link
Author

Thanks for your help.

@Sean-Der
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants