GNOME Bugzilla – Bug 678565
Create an outputfile for remote instance of Insanity tests logs
Last modified: 2012-10-06 11:44:10 UTC
Currently logs from insanity-gst (which is the remote peer of the dbustest) are lost, we already manage that for remote Gst test, but we will need to get that for Insanity logs to The way it works right now might make it complicated to have 2 different files for GSt log and Insanity one, so they might be in the same file for now and let user work around it (cat file |grep insanity |less would make the trick)
Currently we just have all of stdout/stderr in a single outputfile IIRC. That's very useful for debugging as you have everything in sequence there. What would be the use case to separate this?
Ok, so I output everything on stderr and then it will be redirected if needed. commit 00e02d7142254ae3ea92ce2ae773b3d4c8f64d4c Author: Thibault Saunier <thibault.saunier@collabora.com> Date: Tue Jun 26 12:30:51 2012 -0400 lib: Let insanity tests be debuged even if not running standalone And output on stderr so it get printed on time Fixes #678565 Create an outputfile for remote instance of Insanity tests logs
(In reply to comment #1) > Currently we just have all of stdout/stderr in a single outputfile IIRC. That's > very useful for debugging as you have everything in sequence there. You are assuming the various runs have anything to do with each other. If I run play-test on 1000 files, they have nothing to do with each other. > > What would be the use case to separate this? so that I don't have to search through a multi-giga file for the test run I'm interested in.
GST_DEBUG=5 insanity-run --terminal-redirection -T tests -t play-test -a uri:constant:file:///media/data/Videos/Kiwi.flv This outputs something but not the complete GStreamer debug logs. And also not the complete output that you get from running tests/insanity-test-gst-play --run uri=file:///media/data/Videos/Kiwi.flv
*** Bug 678942 has been marked as a duplicate of this bug. ***
insanity-run -T tests -t play-test -a uri:constant:file:///media/data/Videos/Kiwi.flv\;global-gst-debug-level:constant:3\;log-level:constant:3 --terminal-redirection Gives me the GStreamer debug logs now but not the insanity debug output except a single line: 0:00:02.000270516 0x12e6c50 info default insanitygstpipelinetest.c:401 Got EOS from pipeline, and we reached initial state, quitting
Also it is still just using GST_DEBUG and not the functions to set it. Without the functions it will not be possible to use different values for every start/stop iteration.
Created attachment 217648 [details] [review] Patch making change between iterations of start/stop effective (copy/pasting code from gst.c)
Created attachment 217649 [details] [review] Same patch depending on #626462
Comment on attachment 217648 [details] [review] Patch making change between iterations of start/stop effective (copy/pasting code from gst.c) Let's get this in now until the API is exposed in GStreamer
commit b6734d9f1e5444a344f595abcfc4b4b115ed4788 Author: Thibault Saunier <thibault.saunier@collabora.com> Date: Fri Jun 29 13:29:14 2012 -0400 lib: Make debug level change between iterations of start/stop actually effective commit 7e6a713a88ab6f513f3e6ffd76b9fd26d1745a86 Author: Thibault Saunier <thibault.saunier@collabora.com> Date: Fri Jun 15 16:58:03 2012 -0400 gsttest: Add arguments to manage GStreamer debug logging level We need 2 arguments for that as we will want in some case to manage the log level on a non global basis (which would happen when we need more detail about a particular failure, in which case we would raise the level) but have a default that would