action #1311

Improve debugging capabilities for the OS

Added by aplanas about 6 years ago. Updated 4 months ago.

Status:ResolvedStart date:27/01/2014
Priority:LowDue date:
Assignee:okurz% Done:

0%

Category:Feature requests
Target version:QA - future
Difficulty:
Duration:

Description

When a test spots a problem in the system, the user needs to find the error and document it in bugzilla. We need to provide better tools to the user to replicate the bug in a local image, or to simplify the acquisition of the HDD image (using deltas based on isodelta) to dig into the problem

History

#1 Updated by coolo over 5 years ago

  • Category set to 138

#2 Updated by RBrownSUSE over 4 years ago

  • Category changed from 138 to Feature requests

Recategorised - not something that should be implemented in a test

#3 Updated by okurz about 3 years ago

  • Priority changed from Normal to Low
  • Target version set to future

much requested, never properly specified what it means -> no one will work on it that easily.

#4 Updated by okurz over 1 year ago

  • Target version changed from future to future

#5 Updated by okurz 4 months ago

  • Status changed from New to Resolved
  • Assignee set to okurz

I think with record_soft_failure we have good means to track bugs in tests and also apply workarounds. With the post_fail_hook we can gather more than enough data from failing tests, e.g. log files. With test parameters as documented in http://open.qa/docs/#_backend_variables_for_faster_test_execution we can skip unnecessary parts for easier and faster reproduction. With http://open.qa/docs/#_triggering_tests_based_on_an_any_remote_git_refspec_or_open_github_pull_request we can allow easy access to production instances for users that do not want or can't setup a local openQA instance. With openqa-clone-job we can easily trigger jobs based on existing ones.

Also available in: Atom PDF