Project

General

Profile

Actions

action #38090

closed

[sle][functional] Do not mask systemd timers on system_performance scenarios

Added by SLindoMansilla over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
-
Start date:
2018-07-02
Due date:
% Done:

0%

Estimated time:
Difficulty:
easy

Description

system_performance scenarios are aimed to test performance issues like the one caused by btrfs-balance.

See https://openqa.opensuse.org/tests?match=system_performance

In order to not affect other tests, we assume that executing those services on a controlled environment, can reduce drastically the effect on consequent executions of those services (btrfs-balance, btrfs-scrub, snapper-cleanup).

In order to verify that assumtion, system_performance scenarios should cover performance issue on that regard. They should execute the test module force_cron_run but they should not mask the systemd timers that execute those services (see https://progress.opensuse.org/issues/31351, which PR https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5097 masked services to make all other tests free of that problem).

Acceptance criteria

  • AC1: The test module force_cron_run is still scheduled for system_performance scenarios
  • AC2: On system_performance scenarios the systemd timers for maintenance tasks are not masked.
  • AC3: On the rest of scenarios, systemd timers are still masked on force_cron_run.

Tasks

  1. Fix test module: tests/console/force_cron_run.pm

Further information


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally)Resolvedzluo2018-02-032018-07-03

Actions
Actions #1

Updated by SLindoMansilla over 6 years ago

  • Related to action #31351: [functional][u][medium] force_cron_run does not actually run any crons (occasionally) added
Actions #2

Updated by okurz over 6 years ago

  • Status changed from New to In Progress
  • Assignee set to okurz
Actions #4

Updated by okurz over 6 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF