Project

General

Profile

Actions
Copy link

action #12272

closed

Tumbleweed to Tumbleweed Next tests

Added by dimstar almost 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
New test
Target version:
-
Start date:
2016-06-08
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

In order to prevent issues like described ni https://lists.opensuse.org/opensuse-factory/2016-06/msg00113.html we need to have a test that

  • Installs a CURRENT snapshot of Tumbleweed (as published on download.opensuse.org)
  • Upgrades that snapshot to Tumbleweed-NEXT (whatever snapshot openQA is busy testing)

The issues seen here were masked as 'larger' updates (from Leap, 13.2, ...) also installed many other packages that 'transparently' fixed the issue again during the installation - yet users are updating from TW to TW regularly - they might be hit by such issues.

Actions
Copy link
 #1

Updated by okurz almost 8 years ago

  • Category set to New test
Actions
Copy link
 #2

Updated by dimstar almost 8 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

openSUSE Tumbleweed received two new test runs

  • Install a Tumbleweed machine, based on the 'currently' (at the time of the test run) published version (tumbleweed-image)
  • upgrade that machine (using zdup) to the new snapshot being tested (zdup_tw2twnext_gnome)

(the tests are based on GNOME, as it's less forgiving on startup than KDE)

No test code needed to be written, only test suites configured.

tumbleweed-image

DESKTOP=gnome
HDDSIZEGB=40
INSTALLONLY=1
NETBOOT=0 (! This ensures that the net installer uses the pre-configured addresses !)
PUBLISH_HDD_1=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-Tumbleweed@%MACHINE%.qcow2
QEMU_COMPRESS_QCOW2=1
YAST_SW_NO_SUMMARY=0

zdup_tw2twnext_gnome

DESKTOP=gnome
HDD_1=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-Tumbleweed@%MACHINE%.qcow2
START_AFTER_TEST=tumbleweed-image
ZDUP=1
Actions
Copy link

Also available in: Atom PDF