Per the discussion in gaia-ui-automation, called "Bluetooth tests with remote partner", it was discussed that it would be a good idea to have the bluetooth checking from the host removed, because it would be difficult to get that working from an external lab. If we make that part of the test depend on whether a testvars variable exists, we could keep that part of the test and control it if we want to have it enabled or not.
Something like this?
Comment on attachment 8544567 [details] [review] bluetooth Looks like the way to go. If I understood correctly, we won't have a Bluetooth Host at all once we migrate to the new lab. I think we can get rid of it entirely. If we do so, we can also remove everything after: > self.assertTrue(self.data_layer.get_setting('bluetooth.visible'))
Attachment #8544567 - Flags: feedback?(jlorenzo) → feedback+
Comment on attachment 8544567 [details] [review] bluetooth This would work, though I added some comments about additional assertions we could add. Also, I wonder if it's really useful to keep this. Simply not adding (or mistyping) a key to a test variables file would cause this not to run, and it would be hard to know that we're losing coverage.
Attachment #8544567 - Flags: feedback?(dave.hunt) → feedback+
Ok, I'll just remove the bluetooth host checking part. Making the summary reflect that.
Summary: Change test_toggle_bluetooth_settings so that bluetooth host checking is depending on a testvars setting → Remove bluetooth host checking in test_toggle_bluetooth_settings
Comment on attachment 8544567 [details] [review] bluetooth Ok, this should address the feedback/review.
Comment on attachment 8544567 [details] [review] bluetooth r=me with a couple of nits addressed
Attachment #8544567 - Flags: review?(dave.hunt) → review+
Ok, addressed the nits.
Comment on attachment 8544567 [details] [review] bluetooth Executed adhoc job, we have 2 intermittent failures. Can you look at them?  http://jenkins1.qa.scl3.mozilla.com/view/UI/job/flame-kk.ui.adhoc/550
Martijn: Could you take another look at this? I'd like to include this test in our remote lab suite.
Sorry, I forgot about this bug, because I forgot to assign it to me. I need to look at the failures mentioned in comment 8. Note that there is some comments in bug 1116744 that might help to solve that. Also I noticed that Bebe just commented with some improvements for my pull request.
Assignee: nobody → martijn.martijn
Unfortunately, I got a test failure with the test, which seems like a bug in current master build (bluetooth basically doesn't work). I filed bug 1129693 for that.
Depends on: 1129693
Updated the pull request with Florin's comments, I kicked off a new Jenkins try run to see if the intermittent failures are still happening: http://jenkins1.qa.scl3.mozilla.com/job/flame-kk.ui.adhoc/666/
Comment on attachment 8544567 [details] [review] bluetooth I don't see any intermittent failures occuring with this Jenkins try run, so I guess that failure has disappeared somehow. Asking review for review to see if this addressed the comments he added in the pull request.
Comment on attachment 8544567 [details] [review] bluetooth test is failing and we need to remove unused dependencies
Attachment #8544567 - Flags: review?(florin.strugariu) → review-
Comment on attachment 8544567 [details] [review] bluetooth I can't reproduce the failure that Florin is seeing, nor is Jenkins affected by it. Tomorrow, Florin is going to try and find out where that failure is coming from.
Attachment #8544567 - Flags: review- → review?(florin.strugariu)
Attachment #8544567 - Flags: review?(florin.strugariu) → review+
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
(In reply to Dave Hunt (:davehunt) from comment #9) > Martijn: Could you take another look at this? I'd like to include this test > in our remote lab suite. Dave, I think you can now include it in the remote lab suite.
Yep, already done. Thanks Martijn!
I just removed the remaining references to pybluez as it's no longer used: https://github.com/mozilla-b2g/gaia/commit/d99f069f1ef2ff29fa6d7043cf90e65417367e33
You need to log in before you can comment on or make changes to this bug.