action #29945

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

Added by nicksinger about 2 years ago. Updated 12 months ago.

Status:RejectedStart date:17/10/2017
Priority:LowDue date:26/03/2019
Assignee:okurz% Done:

0%

Category:New testEstimated time:3.00 hours
Target version:QA - future
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 about 2 years ago

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

#3 Updated by mgriessmeier about 2 years ago

  • Due date deleted (17/01/2018)

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

#4 Updated by okurz about 2 years ago

  • Target version changed from Milestone 13 to Milestone 14

#5 Updated by okurz about 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 almost 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 over 1 year ago

  • Target version changed from future to future

#8 Updated by riafarov 12 months 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 12/03/2019

#9 Updated by riafarov 12 months ago

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

#10 Updated by riafarov 12 months ago

  • Estimated time set to 3.00

#11 Updated by okurz 12 months 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