plainbox: xml-exporter is not exporting comments

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

Bug Description

Plainbox Version: 0.2+bzr2082+bzr10~raring1

A job failed due to an unmet requirement:

- audio/alsa_record_playback_automated: not-supported
comments: job cannot be started: resource expression "package.name == 'python-gst0.10'" evaluates to false
inhibitors:
  * resource expression "package.name == 'python-gst0.10'" evaluates to false

Python-gst0.10 is not present on raring so the failure to run is correct. The problem is that the comment field in the XML report is not set in this case. Look at this fragment:

    <question name="audio/alsa_record_playback_automated">
      <answer type="multiple_choice">skip</answer>
      <answer_choices>
        <value type="str">none</value>
        <value type="str">pass</value>
        <value type="str">fail</value>
        <value type="str">skip</value>
      </answer_choices>
      <comment></comment>

Plainbox knows what caused the skip, so it should put that in the comment field, and somehow isn't.

I'll attach the raw XML to this report.

Tags: plainbox

Related branches

Revision history for this message
Daniel Manrique (roadmr) wrote :
tags: added: plainbox
Revision history for this message
Daniel Manrique (roadmr) wrote :

Another job with the same problem:

- mediacard/sd-preinserted: not-supported
comments: job cannot be started: resource expression "device.category == 'CARDREADER'" evaluates to false
inhibitors:
  * resource expression "device.category == 'CARDREADER'" evaluates to false

To reiterate, the job failures themselves will be investigated in separate bugs, this one is about why plainbox is not putting that info in the comment field.

Daniel Manrique (roadmr)
Changed in checkbox:
assignee: nobody → Daniel Manrique (roadmr)
status: New → In Progress
importance: Undecided → High
Revision history for this message
Daniel Manrique (roadmr) wrote :

This was tracked down to a problem in the session state exporter code. Thus, this affected all the exporters since the problem was in the source data they receive. Fixed in the attached merge request \o/

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

This is now fixed in trunk

summary: - plainbox: Jobs skipped due to unmet requirements don't set the comment
- field to explain the skip
+ plainbox: xml-exporter is not exporting comments
Changed in checkbox:
milestone: none → 2013-05-23
status: In Progress → Fix Committed
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.