Project

General

Profile

Actions

action #14832

closed

reload needles and retry does not work

Added by rdodopoulos about 8 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Support
Target version:
-
Start date:
2016-11-16
Due date:
% Done:

0%

Estimated time:

Description

After creating a new needle, "reload and retry" fails every time in the interactive mode. The new needle does not match and the test exits as failed.

In older versions the new needle would match and the test would continue.

For the record, I also added 'ENV-VERSION-12-SP2' tag in my recent failed examples.


Related issues 2 (0 open2 closed)

Related to openQA Project (public) - action #17786: [tools]NFS-less mode: Interactive mode needs to resync needlesClosed2017-03-19

Actions
Is duplicate of openQA Project (public) - coordination #14818: [EPIC] Interactive mode is an usability disasterResolvedmkittler2018-05-23

Actions
Actions #1

Updated by coolo almost 8 years ago

  • Status changed from New to Feedback

it works fine for me - is this production or some instance?

Actions #2

Updated by rdodopoulos almost 8 years ago

This was in production. I have not used this function since then. If it works for you feel free to close this ticket. It seems I don't have access to do it myself.

Actions #3

Updated by rdodopoulos almost 8 years ago

Actually, I just used the reload button and the test exited. This time at my own instance but my openQA server is fully updated.

Actions #4

Updated by okurz over 7 years ago

  • Category changed from 124 to Support
  • Assignee set to okurz
  • Priority changed from Normal to Low

Is it still reproducible? I used the interactive mode more in recent time and could not encounter this problem.

Actions #5

Updated by coolo over 7 years ago

did you use it on an instance with caching?

Actions #6

Updated by okurz over 7 years ago

  • Related to action #17786: [tools]NFS-less mode: Interactive mode needs to resync needles added
Actions #7

Updated by okurz over 7 years ago

  • Priority changed from Low to Normal

I could reproduce the issue on the production instance as described on #17786. Apparently my memory was wrong. I consider this blocked by #17786 now anyway.

Actions #8

Updated by okurz over 7 years ago

  • Assignee deleted (okurz)

waiting for blocking ticket

Actions #9

Updated by coolo about 7 years ago

Actions #10

Updated by coolo about 7 years ago

  • Status changed from Feedback to Rejected

To simplify the backlog, I'm closing this as dup of 14818

Actions

Also available in: Atom PDF