Project

General

Profile

Actions
Copy link

action #105271

open

[opensuse]test fails in vagrant:tumbleweed

Added by dimstar over 2 years ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
dancermak
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-01-21
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_vagrant@64bit fails in
tumbleweed

The vagrant test is unreliable,as the image of snapshot under test uses published repo to further perform installations, thus creating invalid results.
When the differences are small enough/ compatible, the test passes. Often times it does not

Test suite description

Maintainer: dancermak. Test vagrant, vagrant plugins and the vagrant boxes

Reproducible

Fails since (at least) Build 20220121

Expected result

Last good: 20220120 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by dimstar over 2 years ago

  • Subject changed from test fails in tumbleweed to test fails in vagrant:tumbleweed
Actions
Copy link
 #2

Updated by maritawerner over 2 years ago

  • Subject changed from test fails in vagrant:tumbleweed to [opensuse]test fails in vagrant:tumbleweed
Actions
Copy link
 #3

Updated by openqa_review about 2 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: extra_tests_vagrant
https://openqa.opensuse.org/tests/2178260

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

Updated by openqa_review about 2 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: extra_tests_vagrant
https://openqa.opensuse.org/tests/2201884

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
Actions
Copy link
 #5

Updated by openqa_review about 2 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: extra_tests_vagrant
https://openqa.opensuse.org/tests/2259735

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 56 days if nothing changes in this ticket.

Actions
Copy link
 #6

Updated by dimstar over 1 year ago

  • Status changed from New to Resolved

Vagrant tests have been passing reliably for the last weeks; the last issues identified were https://bugzilla.opensuse.org/show_bug.cgi?id=1200894 (fixed)

Actions
Copy link
 #7

Updated by dimstar 3 months ago

  • Status changed from Resolved to New

This has actually never been addressed - just that the diff between the published snapshot and the snapshot under test tend to be small enough.

Currently, we have a new version of ncurses in the snapshot to test - which exposes this problem again:

https://openqa.opensuse.org/tests/3880311#step/tumbleweed/40

According the error, a 'solution' is to downgraded libncurses - which can only happen due to the test using external repos, not the one of 'the next snapshot to published, hosted on openQA'

Actions
Copy link
 #8

Updated by dimstar 3 months ago

The error does happen sporadically of course: previous instance e.g. https://openqa.opensuse.org/tests/3865319#step/tumbleweed/40 (snapshot 0111 being tested)

Actions
Copy link
 #9

Updated by openqa_review 3 months ago

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

This bug is still referenced in a failing openQA test: extra_tests_vagrant
https://openqa.opensuse.org/tests/3910952#step/tumbleweed/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
Copy link
 #10

Updated by openqa_review about 2 months ago

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

This bug is still referenced in a failing openQA test: extra_tests_vagrant
https://openqa.opensuse.org/tests/3995176#step/tumbleweed/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 56 days if nothing changes in this ticket.

Actions
Copy link

Also available in: Atom PDF