xvfb-run should be integrated better

Bug #610172 reported by Aaron Bentley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

We usually want to run our tests headless, so both test_on_merge and the testresources config cause xvfb-run to be invoked. This is code duplication, and is also inefficient, because xvfb may not be needed to run the specified tests.

Instead, it would make sense to invoke xvfb only when running selenium tests, and to turn off xvfb according to a commandline flag like "--show-browser".

Revision history for this message
Gary Poster (gary) wrote :

+1 on the idea. Low importance right now, but would be happy for Foundations to be a resource to help someone who wants to fix this.

I don't know enough about the Windmill layer integration to know if this would be relatively easy.

Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Robert Collins (lifeless) wrote :

We could just wrap the mozilla execution in xvfb-run.

Curtis Hovey (sinzui)
description: updated
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.