checkbox-certification (against which this bug is filed) is run only against systems in our certification lab, not by end-users. It is run in the daily testing process which includes a wipe and reinstall of each system and has no end-user interaction. Any crash reports gathered would be ones that were created immediately after a clean install and startup or from running the automated tests.
The goal is to be able to take crash dumps from freshly installed systems that have had some automated test coverage and file bugs based on those dumps. As we have access to the systems and can reproduce the steps that led to the crash (including reinstalls as needed), we have a great opportunity to find and fix bugs. Since this is run internally only, we will not be gathering any information from end-users or annoying them unnecessarily.
If there is additional processing that needs to take place before creating a bug based on this crash data, we'd be happy to do this. Is there a process we can automate to perform this, or is this new functionality that we need to look into?
Martin,
checkbox- certification (against which this bug is filed) is run only against systems in our certification lab, not by end-users. It is run in the daily testing process which includes a wipe and reinstall of each system and has no end-user interaction. Any crash reports gathered would be ones that were created immediately after a clean install and startup or from running the automated tests.
The goal is to be able to take crash dumps from freshly installed systems that have had some automated test coverage and file bugs based on those dumps. As we have access to the systems and can reproduce the steps that led to the crash (including reinstalls as needed), we have a great opportunity to find and fix bugs. Since this is run internally only, we will not be gathering any information from end-users or annoying them unnecessarily.
If there is additional processing that needs to take place before creating a bug based on this crash data, we'd be happy to do this. Is there a process we can automate to perform this, or is this new functionality that we need to look into?