Autopilot video recording fixture is not configured by default

Bug #1365820 reported by Thomi Richards
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Autopilot
Fix Released
High
Unassigned
autopilot (Ubuntu)
New
Undecided
Unassigned
Vivid
New
Undecided
Unassigned

Bug Description

As per IRC conversation:

<thomi> veebers: I just found a bug in the video record stuff :(
<veebers> thomi: oh? :-\ what's the bug?
<thomi> well..
<thomi> get_video_recording_fixture() is returning None
<thomi> which means that when we do this in AutopilotTestcase.setUp:
<thomi> self.useFixture(get_video_recording_fixture()(self))
<thomi> we get:
<thomi> TypeError: 'NoneType' object is not callable
<thomi> looking at the code in _video.py
<thomi> the only way I can see that this might happen is if configure_video_recording was never called, which is a distinct possibility
<thomi> you can't rely on the fact that the user will be using the autopilot test runner
<veebers> right, that's true
<thomi> in fact, I'm surprised this code landed - I assumed that CI would use testtools.run to run our tests
<thomi> I'll submit a bug and a patch now...

Related branches

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:autopilot at revision 513, scheduled for release in autopilot, milestone 1.4

Changed in autopilot:
status: In Progress → Fix Committed
Changed in autopilot:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.