There is no possible way to use domain sockets in the tcp tests

Bug #988257 reported by Manuel de la Peña
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntuone-dev-tools
Status tracked in Trunk
Stable-4-0
Fix Released
Undecided
Unassigned
Trunk
Fix Released
Medium
Manuel de la Peña
ubuntuone-dev-tools (Ubuntu)
Fix Released
Undecided
Unassigned
Quantal
Fix Released
Undecided
Unassigned

Bug Description

Currecntly the tcp test cases do not allow to run tests on domain sockets this should be allow to ensure that test can be run using that transport.

Related branches

Changed in ubuntuone-dev-tools:
importance: Undecided → Medium
status: New → In Progress
assignee: nobody → Manuel de la Peña (mandel)
Changed in ubuntuone-dev-tools:
status: In Progress → Fix Committed
dobey (dobey)
Changed in ubuntuone-dev-tools (Ubuntu Quantal):
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntuone-dev-tools - 3.99.0-0ubuntu1

---------------
ubuntuone-dev-tools (3.99.0-0ubuntu1) quantal; urgency=low

  * New upstream release.
    - Expose squid startup errors when it fails. (LP: #985004)
    - Default to gi/gtk3 reactors and fallback to glib/gtk2 on Linux.
    - Allow using domain sockets instead of TCP in tests. (LP: #988257)
    - Clean up ServerTestCase properly to avoid dirty reactor. (LP: #1002834)
  * debian/watch:
    - Update watch file to use stable-4-0 series for Quantal.
 -- Rodney Dawes <email address hidden> Tue, 05 Jun 2012 13:17:20 -0400

Changed in ubuntuone-dev-tools (Ubuntu Quantal):
status: Triaged → 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.