Project

General

Profile

Actions

action #103954

closed

openQA Project (public) - coordination #64746: [saga][epic] Scale up: Efficient handling of large storage to be able to run current tests efficiently but keep big archives of old results

openQA Project (public) - coordination #80546: [epic] Scale up: Enable to store more results

coordination #96974: [epic] Improve/reconsider thresholds for skipping cleanup

Run asset cleanup concurrently to results based on config on o3 as well

Added by okurz about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

motivation

see #96974

acceptance criteria

  • AC1: Same as on OSD we have concurrent cleanup on O3

suggestions

  • Enable it on o3 and watch

Related issues 1 (0 open1 closed)

Copied from openQA Infrastructure (public) - action #98922: Run asset cleanup concurrently to results based on configResolvedmkittler2021-09-20

Actions
Actions #1

Updated by okurz about 3 years ago

  • Copied from action #98922: Run asset cleanup concurrently to results based on config added
Actions #2

Updated by okurz about 3 years ago

  • Due date set to 2021-12-28
  • Status changed from In Progress to Feedback

I set concurrent = 1 on o3 now. Will check in the following days if that causes any problems.

Actions #3

Updated by okurz about 3 years ago

  • Due date deleted (2021-12-28)
  • Status changed from Feedback to Resolved

I have checked the minion dashboard and found no problems. There are currently no failed jobs on https://openqa.opensuse.org/minion/jobs?state=failed

Actions

Also available in: Atom PDF