Invalid IDs when running in qemu-emulated ARM (FTBFS in tests)

Bug #1195497 reported by Thomi Richards
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
autopilot-gtk
Low
Unassigned

Related branches

Revision history for this message
Martin Pitt (pitti) wrote :

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.

Changed in autopilot-gtk:
importance: Undecided → Low
status: New → Triaged
summary: - Autopilot-gtk FTBFS for ARM
+ Autopilot-gtk FTBFS for qemu-emulated ARM
Martin Pitt (pitti)
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 :

Fix committed into lp:autopilot-gtk at revision 53, scheduled for release in autopilot-gtk, milestone Unknown

Changed in autopilot-gtk:
status: In Progress → Fix Committed
Martin Pitt (pitti)
Changed in autopilot-gtk:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers