QA » openQA Project » openQA Tests

This ticket failed multiple times in the past several builds.
And seems most of the failure occurred with "WebSocketsTest" function.

I am wondering there are some performance problems there, but can't understand why sp4 hits the issue more often.

Re-run with 4GB memory
http://openqa.suse.de/t9197005

In my opinion, the multiplayer drawboard example is prone to needle mismatch, because it requires the use of sending page downs and page ups, and needle matching will depend on screen size parameters among other factors.
I believe, in the sake of stability, that we can safely delete the function that tests the drawboard example.
We already cover the rest of Tomcat's WebSocket examples, and, in reality, this drawboard example is not really tested with multiple connections as it would ideally be the case.
So as far as coverage is concerned we should be ok.

geor wrote:

In my opinion, the multiplayer drawboard example is prone to needle mismatch, because it requires the use of sending page downs and page ups, and needle matching will depend on screen size parameters among other factors.
I believe, in the sake of stability, that we can safely delete the function that tests the drawboard example.
We already cover the rest of Tomcat's WebSocket examples, and, in reality, this drawboard example is not really tested with multiple connections as it would ideally be the case.
So as far as coverage is concerned we should be ok.

Thanks much!
That can explain my I can't fix the issue by increasing the mem size and timeout value. It is not a performance issue.
Let me try to delete this function and see.

#openqa-clone-job  --from http://openqa.suse.de --host http://openqa.suse.de 9207213 _GROUP_ID=0 -skip-download --skip-chained-deps BUILD=tomcat_drawboard_4g _timeout QEMURAM=4096 CASEDIR=https://github.com/rfan1/os-autoinst-distri-opensuse.git#tomcat_multiplayer_drawboard

http://openqa.suse.de/tests/9208390#next_previous
Good news: In past 15 Runs, only failed once and seems caused by page refreshing issue.