GNOME Bugzilla – Bug 678622
Create a different log file PER test instance
Last modified: 2012-10-06 11:44:17 UTC
Since the switch to re-using remote test runners, the gstreamer debug logs are all stored in one gigantic file per process (as opposed to one per test). This makes it close to impossible to do any useful log searching. In addition, setting the gst debug log settings should be possible per test. An example is the following: * Run a test without any gst debugging activated (so that it runs quickly) * If the test fails, re-run it with extra debugging activated (so you get as much details as possible)
Is it even possible to change the debug levels and categories after gst_init() in GStreamer? But yes, having support for per-iteration outputfiles would be good.
> Is it even possible to change the debug levels and categories after gst_init() > in GStreamer? Of course!
(In reply to comment #1) > Is it even possible to change the debug levels and categories after gst_init() > in GStreamer? gst_debug_set_default_threshold() gst_debug_set_threshold_for_name() ...
commit 479d889f9f380a40338f247ef95370c1be813f14 Author: Thibault Saunier <thibault.saunier@collabora.com> Date: Mon Jun 18 09:56:48 2012 -0400 insanity: Make Monitor aware of start/stop iterations .... to commit bb858e6f7616984b20371ebb47e95992d1af953f Author: Thibault Saunier <thibault.saunier@collabora.com> Date: Tue Jun 19 12:06:39 2012 -0400 insanity: Store monitor for each iteration of start/stop We were only storing it once for all at the end of the test and thus it was only avalaible for the last iteration of start/stop of the test, we need it to be visible for user for each iteration.