Comment 3 for bug 1084601

Thinking about this a bit, it might be good to handle this as a warning in some way. We don't want these issues to slide under our radar, but at the same time it's not productive to have to rerun Bluetooth tests because of this. The tests should spit out 'BT is soft blocked, unblocking for test purposes' and then run the actual test. At this point the question is whether to fail or pass the test. Failing it makes the problem of it being blocked more noticable, but clogs up the results. I'll have to make a call on that. Potentially the test can also point out hard block, but that cannot be removed prior to the test, so it will fail anyway.