[Bug 678837] New: Failure to start tests without specifying an stdout/stderr file

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=678837
  GStreamer | gst-qa-system | 0.11.x

           Summary: Failure to start tests without specifying an
                    stdout/stderr file
    Classification: Platform
           Product: GStreamer
           Version: 0.11.x
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: Normal
         Component: gst-qa-system
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: slomo at circular-chaos.org
         QAContact: gstreamer-bugs at lists.freedesktop.org
                CC: thibault.saunier at collabora.com
     GNOME version: ---


$ 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):
  File "/home/slomo/Projects/gstreamer/head/insanity/insanity/dbustest.py",
line 194, in setUp
    self._stdout, self._stderr)
  File "/home/slomo/Projects/gstreamer/head/insanity/insanity/threads.py", line
248, in __init__
    self.setStdoutFile(outfile_path)
  File "/home/slomo/Projects/gstreamer/head/insanity/insanity/threads.py", line
271, in setStdoutFile
    self._stdoutfile = open(outfile_path, "a")
TypeError: coercing to Unicode: need string or buffer, NoneType found
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?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.