I don't necessarily think it's the virt test that's outputting crazy stuff, but it may be the case. In order to know for sure, it would be useful to have the saved session for analysis. Could you:
- Install plainbox (should be available from the same place where checkbox was installed)
- run
plainbox list
it will output a list of sessions that look like:
session pbox-blahblah app:plainbox, flags:['submitted'], title:'some-longish-string'
- Run
plainbox session archive pbox-blahblah my-bug
substituting the blahblah from the output of plainbox list.
After this, a my-bug.tar.gz file will be stored, this contains the raw session data and we can use it to verify which job produced the bogus character, and where it is in the output.
Hey Jeff!
I don't necessarily think it's the virt test that's outputting crazy stuff, but it may be the case. In order to know for sure, it would be useful to have the saved session for analysis. Could you:
- Install plainbox (should be available from the same place where checkbox was installed)
- run
plainbox list
it will output a list of sessions that look like: 'submitted' ], title:' some-longish- string'
session pbox-blahblah app:plainbox, flags:[
- Run
plainbox session archive pbox-blahblah my-bug
substituting the blahblah from the output of plainbox list.
After this, a my-bug.tar.gz file will be stored, this contains the raw session data and we can use it to verify which job produced the bogus character, and where it is in the output.
Thanks!