Merge lp:~cr3/checkbox/network_bandwidth_test into lp:checkbox
Proposed by
Marc Tardif
Status: | Merged |
---|---|
Approved by: | Javier Collado |
Approved revision: | 1433 |
Merged at revision: | 1432 |
Proposed branch: | lp:~cr3/checkbox/network_bandwidth_test |
Merge into: | lp:checkbox |
Diff against target: |
115 lines (+16/-12) 3 files modified
debian/changelog (+1/-0) jobs/networking.txt.in (+4/-1) scripts/network_bandwidth_test (+11/-11) |
To merge this branch: | bzr merge lp:~cr3/checkbox/network_bandwidth_test |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Javier Collado (community) | Approve | ||
Marc Tardif (community) | Needs Resubmitting | ||
Review via email: mp+109917@code.launchpad.net |
Description of the change
Tested on Precise:
$ sudo PYTHONPATH=. ./scripts/
$ echo $?
0
To post a comment you must log in.
Looking at the script and the checkbox jobs that use it, I have a couple of comments:
- It looks like the requirement for package.name == 'nmap' is missing for the jobs generated by networking/ multi_nic, that is, for networking/ multi_nic_ $2.
- I don't like much this regular expression pattern:
alpha_numeric = r"[^ ]+"
because it allows other whitespace characters like \t. I'd say that a better choice would be just r"\S".
- One final comment, just for my own curiosity (not really relevant for this merge request). In networking/ bandwidth I see:
requires:
package.name == 'linux'
package.name == 'ethtool' and package.name == 'nmap'
device.category == 'NETWORK'
and in networking/ multi_nic_ $2 I see:
requires: device.path == "$1" and package.name == 'linux' and package.name == 'ethtool'
My understanding is that multiline requirements are evaluated as if they were linked with an 'and' operator. Is that the case? Is there a practical difference between using multiline vs. single line requirements?