CPO Availability within the registry is nondeterministic
Bug #1457629 reported by
Christopher Lee
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Autopilot |
New
|
Critical
|
Unassigned | ||
Bug Description
It can be confusing when and how a Custom Proxy Object has been (or is) added to the object registry.
The current implementation relies on a metaclass that does some work at runtime/import time.
It should be more explicit to register a class type.
For instance running 2 tests can mean a pass or a fail depending on which is run first if it registers a CPO before the other test (or fail if run the other order etc.).
Related branches
lp:~veebers/autopilot/remove_object_registry-CPO_creation_explicit
- platform-qa-bot: Approve (continuous-integration)
- PS Jenkins bot: Approve (continuous-integration)
- Max Brustkern (community): Approve
-
Diff: 1350 lines (+450/-485)12 files modifiedautopilot/introspection/_object_registry.py (+0/-110)
autopilot/introspection/_proxy_objects.py (+212/-0)
autopilot/introspection/_search.py (+46/-169)
autopilot/introspection/backends.py (+9/-5)
autopilot/introspection/dbus.py (+27/-14)
autopilot/tests/functional/test_dbus_query.py (+6/-0)
autopilot/tests/functional/test_introspection_features.py (+20/-42)
autopilot/tests/unit/test_introspection.py (+11/-8)
autopilot/tests/unit/test_introspection_backends.py (+12/-8)
autopilot/tests/unit/test_introspection_dbus.py (+26/-36)
autopilot/tests/unit/test_introspection_search.py (+0/-93)
autopilot/tests/unit/test_proxy_object.py (+81/-0)
| Changed in autopilot: | |
| importance: | High → Critical |
| Changed in autopilot: | |
| status: | Confirmed → In Progress |
| assignee: | nobody → Christopher Lee (veebers) |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in autopilot: | |
| assignee: | Christopher Lee (veebers) → nobody |
| status: | In Progress → New |
To post a comment you must log in.
I am pretty sure that veebers is not working on this bug.