Project

General

Profile

Actions

action #36109

closed

[functional][y] test fails in yast2_dns_server - improve post_fail_hook or investigation process

Added by okurz about 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Start date:
2018-05-12
Due date:
2018-06-05
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ncurses@64bit fails in
yast2_dns_server
on what I reported as bsc#1093029. y2logs are parsed as for any other yast2_gui test but there is no further investigation in the post_fail_hook or within the test itself.

Reproducible

Fails since (at least) Build 20171029

Acceptance criteria

  • AC1: Service specific information is provided on failures
  • AC2: Enhanced test code can answer the question what the actual state of the systemd service is

Suggestions

  • Get a bit more named-service specific information in the test either as part of normal test flow or in post_fail_hook, e.g. check systemctl status named in post_fail_hook or collect processes with ps aux as we already do in some other post_fail_hooks
  • Think about applying a generic improvement for all yast2_gui test modules

Further details

Always latest result in this scenario: latest

Actions

Also available in: Atom PDF