GNOME Bugzilla – Bug 678837
Failure to start tests without specifying an stdout/stderr file
Last modified: 2012-10-06 11:44:31 UTC
$ insanity-run -T . -t play-test -a uri:constant:file:///media/data/Videos/Kiwi.flv Starting <TestRun object at 0x142bb40 (insanity+testrun+TestRun at 0x1496800)> 2012-06-26 10:12:11,948 0x7f8d30bc0700 ERROR dbustest.py:198:setUp: Error starting the subprocess command ! ['/home/slomo/Projects/gstreamer/head/insanity-gst/tests/insanity-test-gst-play', '--run', '--dbus-uuid=2fbc4d23e115d1bcc6b60429014248e7'] Traceback (most recent call last):
+ Trace 230432
self._stdout, self._stderr)
self.setStdoutFile(outfile_path)
self._stdoutfile = open(outfile_path, "a")
2012-06-26 10:12:11,950 0x7f8d30bc0700 ERROR test.py:331:run: Something went wrong during setup ! Also setting the filenames seems to be done after the thread is started. Will it nonetheless catch all the output and put it into the files?
commit 09578417f0727ff892619b5dc67b670c7ba9ec89 Author: Thibault Saunier <thibault.saunier@collabora.com> Date: Tue Jun 26 11:53:18 2012 -0400 dbustest: Properly handle cases where there is no stderr/stdout redirection Fixes #678837 Failure to start tests without specifying an stdout/stderr file