tests: fix test

Actually do what the comment says. Also keep the old code around, not sure what
should happen when you get a 454 from a TEARDOWN, does it close the connection?
it currently doesn't.
This commit is contained in:
Wim Taymans 2013-06-20 17:30:49 +02:00
parent fa1d3354c0
commit cd8a81b3b1

View file

@ -1011,6 +1011,7 @@ GST_START_TEST (test_play_multithreaded_timeout_client)
GstRTSPSessionPool *pool;
GstRTSPMessage *request;
GstRTSPMessage *response;
GstRTSPStatusCode code;
gst_rtsp_server_set_max_threads (server, 2);
pool = gst_rtsp_server_get_session_pool (server);
@ -1056,11 +1057,20 @@ GST_START_TEST (test_play_multithreaded_timeout_client)
fail_unless (send_request (conn, request));
gst_rtsp_message_free (request);
fail_unless (gst_rtsp_message_new (&response) == GST_RTSP_OK);
fail_unless (gst_rtsp_connection_receive (conn, response, NULL) ==
GST_RTSP_OK);
gst_rtsp_message_parse_response (response, &code, NULL, NULL);
fail_unless (code == GST_RTSP_STS_SESSION_NOT_FOUND);
gst_rtsp_message_free (response);
#if 0
fail_unless (gst_rtsp_message_new (&response) == GST_RTSP_OK);
fail_unless (gst_rtsp_connection_receive (conn, response, NULL) ==
GST_RTSP_ESYS);
fail_unless (errno == ECONNRESET);
gst_rtsp_message_free (response);
#endif
/* clean up and iterate so the clean-up can finish */
g_object_unref (pool);