⚲

Project

General

Profile

Home
Projects
Help

Search:

openQA Tests

All Projects

openQA Tests

Overview
Activity
Roadmap
Issues
Gantt
Calendar
Wiki

Custom queries

All open Feature tests
openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QAM
QE tools team - backlog (ready issues)
QE tools team - backlog (w/o infra)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
SLE15 Migration Open Tickets
SLE15 SP1 Migration Open Tickets
SLE15SP3 Migration open ticket
SLE15SP3 Security open ticket
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #154906

open

[qe-core] set QEMURAM=4G for gnome tests on OSD

Added by rfan1 3 months ago. Updated about 1 month ago.

Status:

In Progress

Priority:

Normal

Assignee:

rfan1

Category:

Enhancement to existing tests

Target version:

QA - QE-Core: Ready

Start date:

2024-01-18

Due date:

% Done:

Estimated time:

Difficulty:

Sprint:

QE-Core: March Sprint 24 (Mar 06 - Mar 28)

Description

Description¶

Background can be found at https://progress.opensuse.org/issues/153808

Action items¶

Modify/change the job settings for job groups which belong to qe-core
Leap tests on OSD need to be fixed as well e.g. https://openqa.suse.de/group_overview/504

Related issues 1 (1 open — 0 closed)

Copied from openQA Tests - action #153808: [qe-core] Adapt first_boot and boot to desktop - DESKTOP=gnome System's ram must be at least 4GB

In Progress

rfan1

2024-01-18

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by rfan1 3 months ago

Copied from action #153808: [qe-core] Adapt first_boot and boot to desktop - DESKTOP=gnome System's ram must be at least 4GB added

Actions

Copy link

Updated by rfan1 3 months ago

Status changed from New to Workable

Actions

Copy link

Updated by rfan1 3 months ago

Status changed from Workable to In Progress
Assignee set to rfan1

Actions

Copy link

Updated by rfan1 3 months ago

Functional job group: https://gitlab.suse.de/qe-core/qa-sle-functional-userspace/-/merge_requests/215
Leap 15.5 incident: https://openqa.suse.de/admin/job_templates/504

Leap 15.6 incident: https://openqa.suse.de/admin/job_templates/541 ¶

Now start to work on qam job groups for sle15sp5

Actions

Copy link

Updated by dzedro 2 months ago

If all tests or most need 4G RAM, I would set it on the top of yaml for arch definition

  ppc64le:
    machine: ppc64le-4g or add settings QEMURAM
    priority: 50

Actions

Copy link

Updated by rfan1 2 months ago

dzedro wrote in #note-5:

If all tests or most need 4G RAM, I would set it on the top of yaml for arch definition
  ppc64le:
    machine: ppc64le-4g or add settings QEMURAM
    priority: 50

It depends on the hardware resource! but I agree with you on this point, we can do this for qam tests, It is a huge task if we modify the setting for each job.

Thanks Jozef!

Actions

Copy link