Project

General

Profile

action #29945

[sle][functional][y][easy] Check releasenotes_origin on s390x

Added by nicksinger over 2 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Low
Assignee:
Category:
New test
Target version:
Start date:
2017-10-17
Due date:
2019-03-26
% Done:

0%

Estimated time:
3.00 h
Difficulty:
Duration: 376

Description

Observation

fate/323273 is tested by the releasenotes_origin test. This test uses (as described in the fate test-case) the installer internal xterm to execute its commands. On s390x openQA fails to open this xterm console. As proposed by okurz we could just simply use the tty there.

Reproducible

Always on s390x

Acceptance criteria

  1. releasenotes_origin is scheduled and work on s390x and is running in the YaST job group

History

#2 Updated by nicksinger over 2 years ago

  • Status changed from In Progress to Workable
  • Assignee deleted (nicksinger)
  • Priority changed from Normal to Low

#3 Updated by mgriessmeier over 2 years ago

  • Due date deleted (2018-01-17)

this was not planned for the sprint, due date was just copied accidentally

#4 Updated by okurz over 2 years ago

  • Target version changed from Milestone 13 to Milestone 14

#5 Updated by okurz over 2 years ago

  • Project changed from SUSE QA tests to openQA Tests
  • Category set to New test
  • Target version changed from Milestone 14 to Milestone 16

#6 Updated by okurz about 2 years ago

  • Subject changed from [sle][functional][easy] Adjust releasenotes_origin to use text-consoles on s390x to [sle][functional][y][easy] Adjust releasenotes_origin to use text-consoles on s390x
  • Target version changed from Milestone 16 to future

#7 Updated by okurz about 2 years ago

  • Target version changed from future to future

#8 Updated by riafarov over 1 year ago

  • Subject changed from [sle][functional][y][easy] Adjust releasenotes_origin to use text-consoles on s390x to [sle][functional][y][easy] Check releasenotes_origin on s390x
  • Description updated (diff)
  • Due date set to 2019-03-12

#9 Updated by riafarov over 1 year ago

  • Due date changed from 2019-03-12 to 2019-03-26

#10 Updated by riafarov over 1 year ago

  • Estimated time set to 3.00 h

#11 Updated by okurz over 1 year ago

  • Status changed from Workable to Rejected
  • Assignee set to okurz

given the low risk and too big effort while still managing a rather big backlog I decide to reject this ticket

Also available in: Atom PDF