SubmissionParser doesn't understand armhf architecture

Bug #1214123 reported by Daniel Manrique
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
High
Unassigned

Bug Description

Even if the udevadm parser produces devices for an armhf device in isolation (i.e. when fed just the udevadm raw output), as a whole the Submission parser doesn't work correctly with armhf devices.

What happens is that the processed data contains no device information, because the udevadm sub-parser is never fired.

Looking at the submission.py code, it appears the udev parser isn't even fired if the "bits" event hasn't been published. This means that both bits and udevadm_result need to have been fired for the parser to be invoked.

The problem seems to be with the "bits" attribute. The architecture as recorded in the submission is compared with a table of known architectures to try to determine the "bits" (basically the architecture's word size, 32 or 64 bits typically). Once a matching architecture is found, the "bits" are set and the udevadm data is processed as requested.

The table that's being used does not contain the armhf architecture, so submissions from this arch will never have udev-extracted devices.

The table lives in checkbox-old/checkbox/parsers/cputable, and is a copy of the dpkg known architectures table, usually found in /usr/share/dpkg/cputable. Even on the latest development version of Ubuntu, this table has no information about armhf.

If I manually add an armhf line, then things work as expected.

Related branches

Daniel Manrique (roadmr)
Changed in checkbox:
status: Triaged → Fix Committed
Ara Pulido (ara)
Changed in checkbox:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.