Project

General

Profile

Actions

action #30889

closed

[opensuse][functional][yast] test fails in yast2_ntpclient - yast2_ntp-client_new_synchronization doesn't match

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

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Start date:
2018-01-24
Due date:
2018-04-10
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-15.0-DVD-x86_64-yast2_ncurses@64bit fails in
yast2_ntpclient

Reproducible

Seems like we simply need a new needle to proceed. Crosscheck with test on tumbleweed.

Fails since (at least) Build 54.1

Expected result

Last good: https://openqa.opensuse.org/tests/638256 (works on TW)

Further details

Always latest result in this scenario: latest

Actions #2

Updated by okurz about 6 years ago

  • Due date changed from 2018-03-13 to 2018-03-27
Actions #3

Updated by okurz about 6 years ago

  • Due date deleted (2018-03-27)
  • Target version changed from Milestone 15 to Milestone 17

sprint13 too full, just as well as M15 and M16

Actions #4

Updated by okurz about 6 years ago

  • Subject changed from [opensuse][functional] test fails in yast2_ntpclient - yast2_ntp-client_new_synchronization doesn't match to [opensuse][functional][yast] test fails in yast2_ntpclient - yast2_ntp-client_new_synchronization doesn't match
  • Due date set to 2018-04-10
  • Target version changed from Milestone 17 to Milestone 15

let's give our "y" team more to fix in short time.

Actions #5

Updated by riafarov about 6 years ago

  • Description updated (diff)
  • Status changed from New to Workable
Actions #6

Updated by riafarov about 6 years ago

  • Assignee set to riafarov
Actions #7

Updated by riafarov about 6 years ago

  • Status changed from Workable to Rejected

Resolved already by needle update.

Actions #8

Updated by okurz about 6 years ago

you already stated the word "resolved", why did you select "rejected" then? I assume because you say it was resolved by some needle update before you took the next step in this ticket but I would call that "resolved". Unless we want to distinguish the tickets that help us to get the work done from those where someone else fixed the job and did not really need the ticket. In this case of course the ticket was kinda useless. I don't know how to solve these cases process-wise though.

Actions

Also available in: Atom PDF