Project

General

Profile

Actions
Copy link

action #65801

closed

[y] test fails in prepare_test_data - no space left on device

Added by mlin7442 over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
riafarov
Category:
Bugs in existing tests
Target version:
SUSE QA (private) - SLE 15 SP3
Start date:
2020-04-18
Due date:
2020-09-22
% Done:

0%

Estimated time:
3.00 h
Difficulty:

Description

Observation

We have same issue on TW: https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=splitusr&version=Tumbleweed#
But there we are lucky not to run out of disk space, in the code we have type_string '1.5G';, so to fix it it's very easy,
but we also want to make this code more reliable and not just smash keys and hope that we did the right thing.
We already have sub resize_partition in lib/partition_setup.pm, so we should reuse it here.

Reproducible

  • Fails since in scenario opensuse-15.2-DVD-x86_64-splitusr@64bit-HD40G
  • Current occurrence: 695.1
  • latest
Actions
Copy link
 #1

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: splitusr@64bit-HD40G
https://openqa.opensuse.org/tests/1251705

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
Copy link
 #2

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: splitusr@64bit-HD40G
https://openqa.opensuse.org/tests/1267199

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
Copy link
 #3

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: splitusr@64bit-HD40G
https://openqa.opensuse.org/tests/1282452

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
Copy link
 #4

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: splitusr@64bit-HD40G
https://openqa.opensuse.org/tests/1302813

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
Copy link
 #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: splitusr@64bit-HD40G
https://openqa.opensuse.org/tests/1316931

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
Copy link
 #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: splitusr@64bit-HD40G
https://openqa.opensuse.org/tests/1316931

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
Copy link
 #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: splitusr@64bit-HD40G
https://openqa.opensuse.org/tests/1316931

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
Copy link
 #8

Updated by SLindoMansilla over 4 years ago

  • Subject changed from test fails in prepare_test_data - no space left on device to [u] test fails in prepare_test_data - no space left on device
Actions
Copy link
 #9

Updated by SLindoMansilla over 4 years ago

  • Subject changed from [u] test fails in prepare_test_data - no space left on device to [y] test fails in prepare_test_data - no space left on device
  • Description updated (diff)

Why should / be 1.5GB?

Actions
Copy link
 #10

Updated by riafarov over 4 years ago

  • Due date set to 2020-09-08
  • Target version set to SLE 15 SP3

There are no Leap 15.3 builds yet, but assets are there, so we can fix this scenario.

Actions
Copy link
 #11

Updated by riafarov over 4 years ago

  • Due date changed from 2020-09-08 to 2020-09-22
Actions
Copy link
 #12

Updated by riafarov over 4 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 3.00 h
Actions
Copy link
 #13

Updated by okurz about 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: splitusr@64bit-HD40G
https://openqa.opensuse.org/tests/1316931

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
Copy link
 #14

Updated by riafarov about 4 years ago

  • Assignee set to riafarov
Actions
Copy link
 #15

Updated by riafarov about 4 years ago

  • Status changed from Workable to Resolved
Actions
Copy link
 #16

Updated by okurz about 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: splitusr@64bit-HD40G
https://openqa.opensuse.org/tests/1316931

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
Copy link
 #17

Updated by okurz about 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: splitusr@64bit-HD40G
https://openqa.opensuse.org/tests/1316931

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
Copy link
 #18

Updated by okurz about 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: splitusr@64bit-HD40G
https://openqa.opensuse.org/tests/1316931

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
Copy link

Also available in: Atom PDF