Project

General

Profile

Actions
Copy link

action #176346

open

coordination #176337: [saga][epic] Stable os-autoinst backends with stable command execution (no mistyping)

coordination #176340: [epic] Stable qemu backend with no unexpected mistyping

[spike][timebox:10h] Clear error indication in the openQA full-stack.t if tests fail with mistyping or lost keys while system is under high load

Added by okurz 2 months ago. Updated 28 days ago.

Status:
New
Priority:
Normal
Assignee:
okurz
Category:
Feature requests
Target version:
QA (public) - future
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Motivation

See #175060 . In the openQA full-stack test t/full-stack.t we observed that we have sometimes test failures which seem to be related to mistyping the command sudo poweroff in the os-autoinst test but not super clear feedback in circleCI about that.

Goals

  • G1: We know how to identify test failures potentially related to high load mistyping
  • G2: The log is not cluttered with too much information

Suggestions

  • Can we detect that "typing" was used, and nothing was typed?
    • Use send_key to send keys to confirm if anything was typed?
  • Make a case of the SUT being under very high load visible in the test results
  • Maybe this was based on high CPU? Or high memory? Or unresponsive I/O?
  • Use stress command to simulate high load on local setup

Related issues 2 (2 open — 0 closed)

Copied from openQA Project (public) - action #175060: [sporadic] [Workflow] Failed: os-autoinst/openQA on master / test (7dc9d82) size:MBlockedgpuliti

Actions
Copied to openQA Project (public) - action #178432: Show the system load before and after t/full-stack.t in circleCI to find out if the load is too highNewokurz2025-03-06

Actions
Actions
Copy link

Also available in: Atom PDF