Invalid IDs when running in qemu-emulated ARM (FTBFS in tests)
Bug #1195497 reported by
Thomi Richards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| autopilot-gtk |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
Related branches
lp:~autopilot/autopilot-gtk/experimental
- PS Jenkins bot: Approve (continuous-integration)
- Martin Pitt (community): Approve
-
Diff: 957 lines (+425/-133)13 files modifieddebian/changelog (+7/-0)
debian/control (+4/-4)
debian/rules (+2/-1)
lib/GtkNode.cpp (+147/-60)
lib/GtkNode.h (+18/-8)
lib/GtkRootNode.cpp (+24/-16)
lib/GtkRootNode.h (+5/-3)
lib/Introspection.cpp (+3/-3)
lib/Variant.cpp (+168/-22)
lib/Variant.h (+3/-1)
lib/autopilot_types.h (+34/-0)
tests/autopilot/tests/test_widget_tree.py (+2/-6)
tests/autopilot/tests/test_xpath_query.py (+8/-9)
Revision history for this message
| Martin Pitt (pitti) wrote | #1 |
| Changed in autopilot-gtk: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| summary: |
- Autopilot-gtk FTBFS for ARM + Autopilot-gtk FTBFS for qemu-emulated ARM |
| summary: |
- Autopilot-gtk FTBFS for qemu-emulated ARM + Invalid IDs when running in qemu-emulated ARM |
| summary: |
- Invalid IDs when running in qemu-emulated ARM + Invalid IDs when running in qemu-emulated ARM (FTBFS in tests) |
| Changed in autopilot-gtk: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Thomi Richards (thomir) |
Revision history for this message
| PS Jenkins bot (ps-jenkins) wrote | #2 |
| Changed in autopilot-gtk: | |
| status: | In Progress → Fix Committed |
| Changed in autopilot-gtk: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This only happens in emulated (qemu) arm instances, there we get some weird negative IDs (like -187681032, but always different). It works fine on real ARM hardware.