Project

General

Profile

Actions

action #42683

closed

[functional][u] Make save_memory_dump work again and re-enable save_memory_dump call in tests/installation/first_boot and other boot modules

Added by okurz over 5 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 31
Start date:
2020-06-23
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Related issues 2 (0 open2 closed)

Related to openQA Tests - action #48671: [opensuse] save_memory_dump make isotovideo to failResolvedokurz2019-03-05

Actions
Copied from openQA Project - action #19390: [tools][sprint 201711.2] qemu "migrate" within testapi::save_memory_dump command never finishes within 2hResolvedszarate2018-01-12

Actions
Actions #1

Updated by okurz over 5 years ago

  • Copied from action #19390: [tools][sprint 201711.2] qemu "migrate" within testapi::save_memory_dump command never finishes within 2h added
Actions #2

Updated by okurz over 4 years ago

  • Related to action #48671: [opensuse] save_memory_dump make isotovideo to fail added
Actions #3

Updated by okurz over 4 years ago

  • Subject changed from [functional][u] Re-enable save_memory_dump call in tests/installation/first_boot with reference to #19390 to [functional][u] Make save_memory_dump work again and re-enable save_memory_dump call in tests/installation/first_boot and other boot modules
Actions #4

Updated by szarate over 4 years ago

  • Status changed from New to Feedback

At least for first_boot: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8501, which is the only module where for now... was being called (aside from LTP)

Actions #5

Updated by okurz over 4 years ago

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

This bug is still referenced in a failing openQA test: skip_registration+workaround_modules
https://openqa.suse.de/tests/3429844

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"
  3. The label in the openQA scenario is removed
Actions #6

Updated by okurz over 4 years ago

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

This bug is still referenced in a failing openQA test: skip_registration+workaround_modules
https://openqa.suse.de/tests/3519641

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"
  3. The label in the openQA scenario is removed
Actions #7

Updated by okurz over 4 years ago

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

This bug is still referenced in a failing openQA test: skip_registration+workaround_modules
https://openqa.suse.de/tests/3562774

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"
  3. The label in the openQA scenario is removed
Actions #8

Updated by okurz over 4 years ago

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

This bug is still referenced in a failing openQA test: skip_registration+workaround_modules
https://openqa.suse.de/tests/3590824

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"
  3. The label in the openQA scenario is removed
Actions #9

Updated by zluo almost 4 years ago

  • Status changed from Feedback to Workable

unassigned, so set it as workable.

Actions #10

Updated by zluo almost 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to zluo
  • Target version changed from future to Milestone 31
  • Start date changed from 2018-01-12 to 2020-06-23
  • % Done changed from 100 to 0
  • Estimated time set to 42.00 h

take over for checking

Actions #11

Updated by zluo almost 4 years ago

  • Status changed from In Progress to Resolved
  • Assignee changed from zluo to szarate

checked:
bootbasetest is already in place in first_boot and boot_to_desktop, so we're fine this.

Actions

Also available in: Atom PDF