QA (public) » openQA Project (public) » openQA Tests (public)

Observation¶

Sometimes reviewers will open tickets like #112514 because the failure is not obvious, if during the post_fail_hook the coredump detection part, sees something... we should make it clear with a record info.

Latest example is:

https://openqa.suse.de/tests/12811611#step/postgresql_server/149

openQA test in scenario sle-15-SP3-Desktop-DVD-Updates-x86_64-qam-regression-message@64bit fails in
groupwise

Acceptance Criteria:¶

1. An info box is displayed when there's a coredump in the SUT.
2. When there's a coredump during the execution of a module, it is exported by the post fail hook

Suggestions¶

For both suggestions a fake asser_screen or assert_script_run call that is guaranteed to fail would cause the PFH to be called & executed:

1. start xterm, then kill -QUIT $xterm_process
2. Use a test program that coredumps

void program_killer (){
  // this generates a segmentation fault
  volatile int *ptr = (int*)0;
  *ptr = 0;
}