wireless_connection tests for 802.11n will run on systems which don't support 802.11n

[Brendan Donegan]

There are seperate tests for 802.11n in Checkbox, but they don't have any requirements about the wireless hardwares support for the 802.11n protocol. This means that systems which only support, e.g. B & G will end up running these tests (and presumably failing them). A mechanism should be in place to ensure that this doesn't happen.

[Jeff Lane  (bladernr)]

Confirming this and setting to low for now.

Brendan, do you think this will cause a problem in testing and needs to be addressed now, or will it just result in "extra testing" that can be ignored for now and addressed later?

[Brendan Donegan (brendan-donegan)]

It will cause false positives to occur on a few systems only, so it's not super urgent.

[Brendan Donegan (brendan-donegan)]

Going to have a look at using cr3/cyphermox's wifi.py script to do this.

[Brendan Donegan (brendan-donegan)]

Moving back to Triaged because this is on the back-burner now for me.

[Daniel Manrique (roadmr)]

Triaging as "job" because ideally the job would require a resource indicating 802.11 protocol support. We don't have that resource now so it can potentially also be a script bug, but since the script doesn't exist, it can't be buggy.. yet :)

[Po-Hsu Lin (cypressyew)]

I think we have one now, the 80211_resource job.
Maybe we could close this bug with Fix-Released?