[opensuse-factory] Needless needles in openQA - -update_123@64bit ?
If -update_123@64bit means what I suppose it does ( i.e. test whether an openSUSE 12.3 upgrade to TW would work ), should it still be part of TW's openQA testing? Likewise for the other tests that seem to refer to older openSUSE versions. Or do we actually want to support this kind of upgrade scenarios? Or are my assumptions completely wrong? Wondering. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, On Wednesday, 5 July 2017 23:26:00 CEST Knurpht - Gertjan Lettink wrote:
If -update_123@64bit means what I suppose it does ( i.e. test whether an openSUSE 12.3 upgrade to TW would work ), should it still be part of TW's openQA testing? Likewise for the other tests that seem to refer to older openSUSE versions.
Or do we actually want to support this kind of upgrade scenarios?
Or are my assumptions completely wrong?
No, not wrong. Well, what is "supported" anyway in openSUSE? It's not SLE ;-) So far these upgrade scenarios are feasible to maintain and showed bugs that people could fix easily or they even showed bug that are valid for openSUSE Tumbleweed regardless of the upgrade base. As long as these tests continue to work fine Dimstar will probably want to keep them in TW tests. When they show a problem that no one will want to fix they will probably be thrown out. Regards, Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op woensdag 5 juli 2017 23:30:40 CEST schreef Oliver Kurz:
Hi,
On Wednesday, 5 July 2017 23:26:00 CEST Knurpht - Gertjan Lettink wrote:
If -update_123@64bit means what I suppose it does ( i.e. test whether an openSUSE 12.3 upgrade to TW would work ), should it still be part of TW's openQA testing? Likewise for the other tests that seem to refer to older openSUSE versions.
Or do we actually want to support this kind of upgrade scenarios?
Or are my assumptions completely wrong?
No, not wrong. Well, what is "supported" anyway in openSUSE? It's not SLE ;-) So far these upgrade scenarios are feasible to maintain and showed bugs that people could fix easily or they even showed bug that are valid for openSUSE Tumbleweed regardless of the upgrade base. As long as these tests continue to work fine Dimstar will probably want to keep them in TW tests. When they show a problem that no one will want to fix they will probably be thrown out.
Regards, Oliver
Thanks for the explanation. I get the point. Still somehow surprised nobody ever ( IME ) brought this up. Plus, I have the impression that the mentioned test for some reason always finishes after all other tests are over and done with. Does it have a low priority? Or is it actually slowing down testing ? -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, 6 July 2017 00:16:27 CEST Knurpht - Gertjan Lettink wrote:
On Wednesday, 5 July 2017 23:26:00 CEST Knurpht - Gertjan Lettink wrote:
If -update_123@64bit means what I suppose it does ( i.e. test whether an openSUSE 12.3 upgrade to TW would work ), should it still be part of TW's openQA testing? Likewise for the other tests that seem to refer to older openSUSE versions.
Or do we actually want to support this kind of upgrade scenarios?
Or are my assumptions completely wrong?
No, not wrong. Well, what is "supported" anyway in openSUSE? It's not SLE ;-) So far these upgrade scenarios are feasible to maintain and showed bugs that people could fix easily or they even showed bug that are valid for openSUSE Tumbleweed regardless of the upgrade base. As long as these tests continue to work fine Dimstar will probably want to keep them in TW tests. When they show a problem that no one will want to fix they will probably be thrown out.
Regards, Oliver
Thanks for the explanation. I get the point. Still somehow surprised nobody ever ( IME ) brought this up. Plus, I have the impression that the mentioned test for some reason always finishes after all other tests are over and done with. Does it have a low priority? Or is it actually slowing down testing ?
I guess it's just taking way longer than other tests because there are more packages to download and install to cover multiple years worth of updates :-) But that's not a bad thing per se because so far our openQA tests do not really test that a system is running stable "for some time". Of course, in the above example, a lot of time is spent in the still old system to download. But anyway, a way to improve the testing could be to split the existing tests into the ones used for acceptance of a new snapshot and other, longer running ones that access the released repositories (after the snapshot got published) and test more and for a longer time. It can't stop a snapshot anymore but still better to catch bugs earlier by automatic tools than users finding it manually. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Knurpht - Gertjan Lettink -
Oliver Kurz