#309 standard-test-source triggers TimeoutException
Closed: INVALID by bgoncalv. Opened by whot.

Full pipeline:
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/detail/fedora-rawhide-pr-pipeline/991/pipeline/

Specific error message:

[2019-03-08T11:55:34.486Z] TASK [standard-test-source : Add executor host] ********************************
[2019-03-08T11:55:34.742Z] changed: [/workDir/workspace/fedora-rawhide-pr-pipeline/images/test_subject.qcow2] => {"add_host": {"groups": [], "host_name": "executor", "host_vars": {"ansible_connection": "local", "ansible_host": "127.0.0.1", "ansible_ssh_connection": "local"}}, "changed": true}
[2019-03-08T11:55:34.742Z] 
[2019-03-08T11:55:34.742Z] TASK [standard-test-source : Gather facts] *************************************
[2019-03-08T11:56:01.741Z] java.net.SocketTimeoutException: sent ping but didn't receive pong within 1000ms (after 347 successful ping/pongs)
[2019-03-08T11:56:01.741Z]  at okhttp3.internal.ws.RealWebSocket.writePingFrame(RealWebSocket.java:546)
[2019-03-08T11:56:01.741Z]  at okhttp3.internal.ws.RealWebSocket$PingRunnable.run(RealWebSocket.java:530)
[2019-03-08T11:56:01.741Z]  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[2019-03-08T11:56:01.741Z]  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
[2019-03-08T11:56:01.741Z]  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
[2019-03-08T11:56:01.741Z]  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
[2019-03-08T11:56:01.741Z]  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[2019-03-08T11:56:01.741Z]  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[2019-03-08T11:56:01.741Z]  at java.lang.Thread.run(Thread.java:748)

Come to think of it, I think I've been getting this one all day for this test role. The few times I thought it was fixed was when something earlier failed (like issue 307)


Thanks for reporting this issue, but this is not an issue on standard-test-roles, but a problem on apps.ci.centos.org. @jbieren is aware of the problem already, I'll close this issue as it is not for STR. @jbieren let me know if I need to open an issue for apps.ci.centos.org (and where would be the best place to report it?)

This messages though shouldn't have caused your tests to fail. What caused the test failure is issue 307 that we need to fix as well.

Metadata Update from @bgoncalv:
- Issue close_status updated to: INVALID
- Issue status updated to: Closed (was: Open)

Metadata