QA (public) &raquo; openQA Project (public)

https://openqa.suse.de/tests/635851/file/autoinst-log.txt

Category:

Feature requests

Target version:

Start date:

2018-05-23

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

Description

observation¶

steps to reproduce¶

Start test
Go in interactive mode in very beginning
Pause test
Test times out

problem¶

H1. a regression in os-autoinst

Subtasks 7 (0 open — 7 closed)

action #36442: Access to running SUTs for System Developers

Resolved

2018-05-23

action #36454: Move 'Minimal developer mode' to openQA web UI

Resolved

2018-05-23

action #36574: Display instructions how to connect when a job is in status waiting

Resolved

szarate

2018-05-28

action #36613: Implement WS connection from web UI to command server

Resolved

2018-05-29

action #37375: Create UI elements for developer sessions and update them via WS connection

Resolved

2018-06-14

action #38120: Make developer mode accesible to non-admins

Resolved

2018-07-03

action #38510: Allow os-autoinst to pause on next assert_screen timeout

Resolved

2018-07-18

Related issues 6 (0 open — 6 closed)

Has duplicate openQA Project (public) - action #14832: reload needles and retry does not work

Rejected

2016-11-16

Has duplicate openQA Project (public) - action #18364: interactive mode - needle editor - reload needles and retry doesn't work on most cases

Closed

2017-04-05

Has duplicate openQA Project (public) - action #18700: openQA worker doesn't work reliable anymore after needle created in interactive mode and reloaded

Closed

2017-04-21

Has duplicate openQA Project (public) - action #18880: fix interactive mode with caching

Closed

2017-04-29

Has duplicate openQA Project (public) - action #19294: openQA webUI - interactive mode - needle editor icon doesn't show up after new needle reloaded

Closed

2017-05-22

Has duplicate openQA Project (public) - action #17786: [tools]NFS-less mode: Interactive mode needs to resync needles

Closed

2017-03-19

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Updated by okurz about 8 years ago

Subject changed from Test got timeout in pause mode to [interactive] Test got timeout in pause mode

Actions

Updated by mkittler about 8 years ago

I can not reproduce it here.

Actions

Updated by asmorodskyi about 8 years ago

Status changed from New to In Progress

issue not reproduces for more than 20 builds
https://openqa.suse.de/tests/latest?distri=sle&limit_previous=50&version=12-SP3&arch=x86_64&flavor=Server-DVD&machine=64bit&test=migration_zdup_offline_sle12sp1#previous
closing

Actions

Updated by asmorodskyi about 8 years ago

Status changed from In Progress to Rejected

Actions

Updated by okurz about 8 years ago

Status changed from Rejected to In Progress

it's interactive mode so the verification with 20 builds does not apply here.

Actions

Updated by coolo almost 8 years ago

Assignee set to coolo

Actions

Updated by coolo almost 8 years ago

Subject changed from [interactive] Test got timeout in pause mode to Interactive mode is an usability desaster
Category changed from Regressions/Crashes to 124
Status changed from In Progress to New
Priority changed from High to Normal

As a matter of fact: there is no "pause mode". The button you pressed is titled 'Stop waiting for needle' - and if you press it, the job will fail unless you create a new needle and reload.

Actions

Updated by okurz over 7 years ago

Related to action #18700: openQA worker doesn't work reliable anymore after needle created in interactive mode and reloaded added

Actions

Updated by coolo about 7 years ago

Subject changed from Interactive mode is an usability desaster to [EPIC] Interactive mode is an usability desaster
Status changed from New to In Progress

I did some research on it during HW - https://hackweek.suse.com/16/projects/openqa-ide

But a severe cold stopped me from any real progress :(

Actions

#10

Updated by coolo about 7 years ago

Has duplicate action #14832: reload needles and retry does not work added

Actions

#11

Updated by coolo about 7 years ago

Has duplicate action #18364: interactive mode - needle editor - reload needles and retry doesn't work on most cases added

Actions

#12

Updated by coolo about 7 years ago

Related to deleted (action #18700: openQA worker doesn't work reliable anymore after needle created in interactive mode and reloaded)

Actions

#13

Updated by coolo about 7 years ago

Has duplicate action #18700: openQA worker doesn't work reliable anymore after needle created in interactive mode and reloaded added

Actions

#14

Updated by coolo about 7 years ago

Has duplicate action #18880: fix interactive mode with caching added

Actions

#15

Updated by coolo about 7 years ago

Has duplicate action #19294: openQA webUI - interactive mode - needle editor icon doesn't show up after new needle reloaded added

Actions

#16

Updated by coolo about 7 years ago

Has duplicate action #17786: [tools]NFS-less mode: Interactive mode needs to resync needles added

Actions

#17

Updated by coolo over 6 years ago

First branches are set to remove what we have - and add a WS to isotovideo for remote control

Actions

#18

Updated by coolo over 6 years ago

User Stories for openQA Developer Mode

We have different developers:

Reviewer Ray wants a way to update needles without job restarts
Test Developer Tim wants a way to maintain tests and needles
System Developer Lea wants a way to access running SUTs

User Stories:

Lea learned from a bug report that gnucash crashes on startup, but can't reproduce in her system. As such she wants openQA to pause before the gnucash test and give her a chance to step through the test process until the crash to continue manually collecting logs. Lea prefers to have direct access to the SUT - vnc or ssh. She does not need nor know openQA test API in general.
Ray reviews the latest build of Tumbleweed and notices a font change breaking all old needles in GUI applications. He wants openQA to pause whenever an assert_screen would timeout to update the needle and redo the assert_screen with that new needle. Ray is working at about 3 scenarios at the same time - covering different areas of needles.
Tim got a ticket from Ray that the docker test failed and wants openQA to reproduce the issue and pause at the beginning of the docker test. Afterwards he wants openQA to make a disk snapshot and step through the test execution to find out where the problem is. After he found out, he reloads the snapshot to tweak the execution. During this process, openQA records his steps and allows to add needles.

Actions