I bet the legacy one produces the expected json output when run through the parser, while the checkbox-ng one doesn't. This is because the summary section of the xml file lacks a few items that are needed for the parser to consider this a complete, valid submission and actually process it. This in turn is caused by not having run some of the mandatory resources. The mandatory resources are:
Now, in Yung's case, the whitelists he's using have the resources listed explicitly in the whitelist, but some of the mandatory ones are not required by any job, which means bug 1302388 is the cause of his problem. A possible solution would be to include miscellanea/submission_resources in those whitelists; we had kept the explicit list of resources for compatibility with checkbox legacy but that's no longer needed so we can potentially prune this.
I remember there was another bug affecting resource running from checkbox-gui, other than that possibility I'd say this bug is a duplicate of byg 1302388, and we can mitigate it with the workaround I mentioned.
OK, I looked at both of Yung's submissions.
I bet the legacy one produces the expected json output when run through the parser, while the checkbox-ng one doesn't. This is because the summary section of the xml file lacks a few items that are needed for the parser to consider this a complete, valid submission and actually process it. This in turn is caused by not having run some of the mandatory resources. The mandatory resources are:
cpuinfo
dmi
dpkg
lsb
package
requirements
uname
This is the summary from a valid submission:
<summary> certification- client" version= "0.19~ubuntu14. 04.1"/> 2014-05- 15T06:51: 01"/> 3.13.0- 24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC d00f84de8a55581 5fa1c4660280da3 08"/>
<architecture value="amd64"/>
<client name="checkbox-
<contactable value="False"/>
<date_created value="
<distribution value="Ubuntu"/>
<distroseries value="14.04"/>
<kernel-release value="
<live_cd value="False"/>
<private value="False"/>
<system_id value="
</summary>
This is the invalid submission's summary:
<summary> 2014-05- 15T06:37: 08"/>
<client name="checkbox-gui" version="0.6.0"/>
<date_created value="
<private value="False"/>
<contactable value="False"/>
<live_cd value="False"/>
<system_id value=""/>
</summary>
Now, in Yung's case, the whitelists he's using have the resources listed explicitly in the whitelist, but some of the mandatory ones are not required by any job, which means bug 1302388 is the cause of his problem. A possible solution would be to include miscellanea/ submission_ resources in those whitelists; we had kept the explicit list of resources for compatibility with checkbox legacy but that's no longer needed so we can potentially prune this.
I remember there was another bug affecting resource running from checkbox-gui, other than that possibility I'd say this bug is a duplicate of byg 1302388, and we can mitigate it with the workaround I mentioned.