DBusIntrospectionObject.select_many documentation should explicitly state that order is not guaranteed
Bug #1248336 reported by
Christopher Lee
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Autopilot |
Fix Released
|
Low
|
Christopher Lee | ||
autopilot (Ubuntu) |
Fix Released
|
Undecided
|
rosa maria |
Bug Description
Currently some tests rely on the list order returned by select_many which makes them flaky and susceptible to breaking on updates.
The documentation should explicitly state that the order is not guaranteed in an attempt to clarify this.
Related branches
lp:~veebers/autopilot/docs_fixes_1248336
- PS Jenkins bot: Approve (continuous-integration)
- Thomi Richards (community): Approve
-
Diff: 19 lines (+5/-2)1 file modifiedautopilot/introspection/dbus.py (+5/-2)
lp:~thomir-deactivatedaccount/autopilot/trunk-object-ordering-docs
- PS Jenkins bot: Approve (continuous-integration)
- Leo Arias (community): Approve
- Christopher Lee (community): Approve
-
Diff: 50 lines (+31/-1)2 files modifiedautopilot/introspection/dbus.py (+5/-1)
docs/tutorial/good_tests.rst (+26/-0)
Changed in autopilot: | |
status: | Fix Committed → Fix Released |
Changed in autopilot (Ubuntu): | |
assignee: | nobody → rosa maria (rprosamaria383) |
assignee: | rosa maria (rprosamaria383) → nobody |
assignee: | nobody → rosa maria (rprosamaria383) |
To post a comment you must log in.
Fix committed into lp:autopilot at revision 357, scheduled for release in autopilot, milestone 1.4