Project

General

Profile

Actions

action #13456

closed

No candidate needles for current step of a running test(?)

Added by AdamWill over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
-
Start date:
2016-08-23
Due date:
% Done:

0%

Estimated time:

Description

In Fedora we're still using openQA git circa July 8 - I will evaluate the changes since then, make appropriate adjustments to our stuff and bump to a newer git at some point, but now isn't a good time.

With that openQA, I seem to have a rather annoying problem with the needle editor. If I use it from a completed job - say, I go to a completed job, click on a failed needle match, and click 'Create new needle' - the editor, properly, has several candidate needles that appear in the 'Needle based on' and 'Copy areas from' drop-downs, letting me conveniently base the new needle on an old one.

But if I run a job in interactive mode to edit needles as I go along, it doesn't work. Whenever a needle match fails and I click the scissors, the editor loads and it knows what tag it was looking for, but it does not show any candidate needles. Which makes creating the new needle a pain in the ass.

I also note that if I just visit the URL for the current step while the needle editor is loaded and behaving badly, there are no entries in the 'Candidate needle:' dropdown.

I did try to figure this out myself and see if any of the later commits fixes it, but I just couldn't, I couldn't manage to figure out how and when the candidate needles are supposed to be populated. Could someone give me a pointer if this has been fixed with a later commit I can backport for now?


Related issues 1 (0 open1 closed)

Blocked by openQA Project - action #12680: interactive mode: stop_waitforneedle is not writing out detailsResolvedmlin74422016-07-13

Actions
Actions

Also available in: Atom PDF