Debugging information should be included in the submission

[Marc Tardif]

When there is a failure with a question, it should be possible to define the relevant information to provide for debugging purposes. This commands to gather this information should be defined in the question definition text file. The actual commands should be packaged in a zip file and referenced in a MANIFEST.

[Marc Tardif (cr3)]

For example, according to the DebuggingACPI page on the Ubuntu wiki, the following information could be specified for an ACPI related test:

debug:
  uname -a
  lspci -vvnn
  dmidecode
  tar -C /proc/acpi -cjf - .

This makes it possible to append almost any kind of debugging information to a test. Furthermore, the output of these commands could be normalized so that it is only sent once in a submission.

[Henrik Nilsen Omma (henrik)]

Alternatively, should we simply define a relevant package in the test definition file, run apport with that package as an argument and file a bug or link to an existing one?

[Marc Tardif (cr3)]

Absolutely, especially considering that the package can be determined from the requires field in a test. If more information is needed in addition to apport, such as running the alsa-info.sh script from the alsa project, should checkbox provide a debug field which would extend apport or should checkbox extend apport with more handlers?

[Marc Tardif (cr3)]

Debugging information on a per test basis has been superseded by attachments which should cover most if not all necessary debugging information across tests. Changing the status to fix released since attachments have been available for a while.