Project

General

Profile

Actions

action #109208

open

[qe-core] test fails in boot_to_desktop - set QEMURAM=2G where DESKTOP=gnome in s390

Added by szarate almost 2 years ago. Updated 9 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-03-30
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

As per: https://bugzilla.suse.com/show_bug.cgi?id=1166955#c10

I have added 2GB ram to jobs in the functional job group, which while fine... does this for all the jobs, so we're not testing the minimum anymore (Within the functional job group)

AC: all tests that use aGNOME=1 scenario, use the Machine ppc64le-2g

See #65064 and https://openqa.suse.de/tests/8407156#step/boot_to_desktop/38


Related issues 2 (0 open2 closed)

Related to openQA Tests - action #65064: [functional][u] Use updated QEMURAM value in jobs with GNOME=1Resolveddheidler2020-03-31

Actions
Related to openQA Tests - action #118357: [qe-core] Use 2GB RAM for all Leap 15.4 upgrade-* scenarios to avoid stalls.Resolvedrfan12022-10-12

Actions
Actions #1

Updated by szarate almost 2 years ago

  • Related to action #65064: [functional][u] Use updated QEMURAM value in jobs with GNOME=1 added
Actions #2

Updated by szarate almost 2 years ago

Added straight to feedback for me to find out if this is also the case on s390. Like for instance, ubuntu lists 4GB for desktops.

Actions #3

Updated by szarate almost 2 years ago

  • Description updated (diff)
Actions #5

Updated by szarate over 1 year ago

  • Due date changed from 2022-04-08 to 2022-07-20

This needs to be an epic

Actions #6

Updated by livdywan over 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #7

Updated by okurz over 1 year ago

cdywan wrote:

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

To correct: Actually the problem is that the due date is exceeded

Actions #8

Updated by slo-gin over 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #9

Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: multipath@ppc64le-no-tmpfs
https://openqa.suse.de/tests/9574366#step/user_settings/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 48 days if nothing changes in this ticket.

Actions #10

Updated by slo-gin over 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #11

Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: multipath@ppc64le-no-tmpfs
https://openqa.suse.de/tests/9574366#step/user_settings/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions #12

Updated by slo-gin over 1 year ago

This ticket is 10 days after the due-date. Please consider closing this ticket or move the due-date accordingly.

Actions #13

Updated by szarate over 1 year ago

  • Related to action #118357: [qe-core] Use 2GB RAM for all Leap 15.4 upgrade-* scenarios to avoid stalls. added
Actions #14

Updated by slo-gin over 1 year ago

This ticket is 10 days after the due-date. Please consider closing this ticket or move the due-date accordingly.

Actions #15

Updated by okurz over 1 year ago

  • Due date deleted (2022-07-20)

This ticket had a due set but exceeded it already by more than 14 days. We would like to take the due date seriously so please update the ticket accordingly (resolve the ticket or update the due-date or remove the due-date). See https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives for details.

Actions #16

Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: multipath@ppc64le-no-tmpfs
https://openqa.suse.de/tests/9574366#step/user_settings/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions #17

Updated by slo-gin 9 days ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF