Project

General

Profile

Actions

action #43613

closed

[functional][u] test fails in rsync

Added by lnussel over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 21
Start date:
2018-11-09
Due date:
2018-11-09
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

the rsync needle does not work at the end of the screen. Maybe add a 'clear' somewhere to avoid that situation?

openQA test in scenario opensuse-15.1:S:D-Staging-DVD-x86_64-textmode@64bit fails in
rsync

Reproducible

Fails since (at least) Build 31.1 (current job)

Expected result

Last good: 30.2 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by okurz over 5 years ago

  • Subject changed from test fails in rsync to [jeos] test fails in rsync
  • Assignee set to ccret
Actions #2

Updated by lnussel over 5 years ago

has nothing to do with JeOS. Was in regular leap stagings

Actions #3

Updated by ccret over 5 years ago

  • Status changed from New to In Progress

There is a clear_console there, but it's in the wrong place. I am changing it now.

Actions #5

Updated by okurz over 5 years ago

lnussel wrote:

has nothing to do with JeOS. Was in regular leap stagings

yes, sorry. I was adding [jeos] to refer to the virtual team that ccret is working in, not the product that the bug was found in.

@ccret, do you have a better tag we could use in tickets?

Actions #6

Updated by ccret over 5 years ago

@okurz not really. Other than jeos I don't think there are other tags for this team.

Actions #7

Updated by okurz over 5 years ago

I see, maybe you can find a better team-label which does not limit to "jeos" to prevent the confusion we had here? :)

Actions #8

Updated by michalnowak over 5 years ago

  • Subject changed from [jeos] test fails in rsync to test fails in rsync

The scope of the test is very general, kinda feels like [sle][functional] to me. If you don't like that, just assign it to the right person :).

Actions #9

Updated by okurz over 5 years ago

  • Subject changed from test fails in rsync to [functional][u] test fails in rsync
  • Target version set to Milestone 21

yes, that would be the right marker regarding the scope but not the "team". Fine, taking it into the backlog of QSF-u but with ccret assigned to track.

@ccret, as the due date has passed, what are your plans regarding this ticket? What's your estimate when you would be done?

Actions #10

Updated by ccret over 5 years ago

  • Status changed from In Progress to Resolved

@okurz sorry, I forgot to mark it resolved. It is done as per the PR above

Actions

Also available in: Atom PDF