Summary: | net-misc/cnetworkmanager fails tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Nirbheek Chauhan (RETIRED) <nirbheek> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | dagger |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
Diego Elio Pettenò (RETIRED)
2009-12-04 20:35:29 UTC
Created attachment 212054 [details]
Build log
You need to have networkmanager running and connected to dbus for the tests to work. I presume that on your tinderbox, you don't have it running, so the tests fail. We really can't do anything about this (starting networkmanager manually will destroy user's current network connection). This is one of the cases where RESTRICT=test would definitely be welcome :P But then users who want to test if cnetworkmanager works with their installation can't do so. I thought that was the primary motivation for FEATURES=test :) Infact, this behaviour (which imo is unavoidable anyway) also helps users make sure their networkmanager is setup properly for use by third-party apps. I think a proper solution would be a way to specify a dependency (use NetworkManager ?) on the NetworkManager init script when src_test is run. And if the init script is not running, tests should just be skipped, or some tests disabled, etc. |