Hardware latency tests, used PC's

More
19 Jun 2020 14:07 #172082 by seuchato

- Default run, works, exist on latency over 25000 as it should,
- Run with no base thread exits properly,
- Run with no base thread when pressing ctrl+c doe snot exit, see bellow,
- Run with base thread at 100000 does not exit cleanly,
- Run with base thread at 100000 when pressing ctrl+c does not exit, see below

----This is the bellow part:
After ctrl+c the terminal will continuously show this:
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  3 (X_GetWindowAttributes)
  Resource id in failed request:  0x5c00002
  Serial number of failed request:  18
  Current serial number in output stream:  19
It does not exit after several ctrl+c, has to be terminated.
So so close.... :)


I'll look into this. Works here. Must have to do with closing the browser window and the xdotools.
greez
chris

Please Log in or Create an account to join the conversation.

More
19 Jun 2020 14:22 #172083 by tommylight
Leme reboot, maybe something left from previous tests

Please Log in or Create an account to join the conversation.

More
19 Jun 2020 14:26 #172084 by seuchato
kill -SIGINT $(ps -A | awk '/latency/{print $1}')

should terminate latency still running in bg

Please Log in or Create an account to join the conversation.

More
19 Jun 2020 15:21 #172086 by seuchato
I can reproduce the errormessages. It seems to be a race condition in xdotool, see here

lcnc-hw closes the browserwindow in my case, but I >think< xdotool "thinks" it is not.

You can do the following:
ps -ef | grep lcnc
root     24118  1241  0 16:37 pts/4    00:00:00 /bin/bash ./lcnc-hw
root     26991  5011  0 16:54 pts/5    00:00:00 grep lcnc
kill -9 24118

Please Log in or Create an account to join the conversation.

More
19 Jun 2020 15:22 - 19 Jun 2020 15:24 #172087 by seuchato
Hope I got it sorted out now. Kindly let me know.

File Attachment:

File Name: lcnc-hw_20...19-3.zip
File Size:5 KB


Edit: could be that sometimes the browser window is not closed automacilly. But now the odd error messages should be gone for good
Attachments:
Last edit: 19 Jun 2020 15:24 by seuchato.
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
19 Jun 2020 15:34 #172090 by tommylight
Looking good, still does not exit but pressing ctrl+c exits cleanly, so we are good.
Will do some more tests on some other equipment, start a new topic and edit the existing one with updated info as i test them.

Please Log in or Create an account to join the conversation.

More
19 Jun 2020 15:45 #172091 by tommylight
It works !
Exits as it should, even with ctrl+c.
No more excuses, now on to testing ! :)

Please Log in or Create an account to join the conversation.

More
19 Jun 2020 15:46 #172092 by seuchato
Kindly be more specific on where it is not cleanly exiting. I have it stopping everyting nicely here, only the browser window sometimes does not close. This is the behaviour that is described in the race condition problem of xdotool. I cannot fix that. Useers will have to live with than and bite sour apple by closing the eventually still running vimeo by hand.

greez chris

PS: be sure to post a link on the new thread here
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
19 Jun 2020 15:51 #172093 by tommylight
That reply was before i saw the new version in your edit, now all is good.
Of course i will post the link here.
Thank you.

Please Log in or Create an account to join the conversation.

More
19 Jun 2020 15:57 #172094 by seuchato
Welcome. About the new thread: is it on my script or the intention of it gathering comparable hw and latency data? Two threads probably.
greez
chris

Please Log in or Create an account to join the conversation.

Time to create page: 0.185 seconds
Powered by Kunena Forum