QA (public) » openQA Project (public) » openQA Tests (public)

what are the differences between openSUSE_Krypton_stable.x86_64-5.7.0-Build11.24.iso and openSUSE_Krypton.x86_64-5.6.90-Build4.51.is

Lower version is probably just a hindsight. The ISOs not marked "stable" target the unstable branches and usually have the beta/RC release numbers. They need to be bumped after a new major release.

can we feed back openQA results to OBS or the ones responsible for building Krypton/Argon?

Yes, yes, yes! Those responsible would be the openSUSE community KDE team. This would be very useful as upstream bugs would be found and hopefully fixed. ;)

can we promote this better, e.g. blog about it?

So far I handled the communication but on my personal blog: see

• https://www.dennogumi.org/2016/06/two-in-one/
• https://www.dennogumi.org/2016/02/adding-wayland-to-the-gas-mixture/
• https://www.dennogumi.org/2016/02/where-are-my-noble-gases-i-need-more-noble-gases/

Not enough time to do more for now.

I'm not knowledgeable enough on openQA to answer the other questions.

• should there be just one job group for all Krypton/Argon or two, one for Krypton, one for Argon, one even more because there are different variants of these, e.g. "Krypton stable"?

As Argon is based on Leap 42.1, it may behave differently. Krypton and Krypton stable shouldn't differ too much except for needles.

• what are the differences between openSUSE_Krypton_stable.x86_64-5.7.0-Build11.24.iso and openSUSE_Krypton.x86_64-5.6.90-Build4.51.iso on http://download.opensuse.org/repositories/KDE:/Medias/images/iso/?

Version number is changed now, but a rebuild will take a while due to the Akonadi splits.

• how should openQA tests be triggered? -> okurz: I assume every change in the file in the download repo, i.e. if the name of the ISO changes

Yup.

• can we feed back openQA results to OBS or the ones responsible for building Krypton/Argon?

Yes, but only if there is a way for the KDE team to update needles. Otherwise it may become annoying to have a ton of expected failures.

[03/08/2016 13:07:24] okurz: hmm.. jobgroups is a tough one - as far as I see it is 'independent products' and I'd thus see one group per product
[03/08/2016 13:07:35] (argon, krypton, krypton-next)
[03/08/2016 13:08:25] ok, will start with just one group for krypton then and add others later --> https://openqa.opensuse.org/admin/job_templates/23

• Created medium on openqa instance (on lord.arch as well as o3)

sudo -u _openqa-worker /usr/share/openqa/script/client products get distri=opensuse version=* flavor=Krypton-Live arch=x86_64 | grep -q Krypton-Live || sudo -u _openqa-worker /usr/share/openqa/script/client products post distri=opensuse version=* flavor=Krypton-Live arch=x86_64 settings[LIVECD]=1 settings[ISO_MAXSIZE]=999999999

• Created job group "openSUSE Krypton" over web ui
• Created testsuite "krypton-live" with settings as LIVETEST=1

• Added medium to job group with testsuite

• Configured http://lord.arch:8080/job/krypton-openqa to trigger iso with

/usr/share/openqa/script/client --host https://openqa.opensuse.org \
    isos post DISTRI=opensuse VERSION=${version} \
    FLAVOR=Krypton-Live BUILD=${build} ARCH=${arch} ISO_URL=${download}${newest_krypton_iso}

using ISO download.

First test on o3 triggered --> t#235811

OBS projects are in https://build.opensuse.org/project/show/KDE:Medias
Using something like https://github.com/openSUSE/osc-plugin-factory/blob/master/openqa-comments.py or
https://api.opensuse.org/apidocs#89 it should be possible to post comments on the corresponding subproject or packages, e.g.

osc api -X POST "/comments/package/KDE:Medias/openSUSE-Krypton…

the comment content is delivered by the data attribute, e.g. like

osc api --data='foo' -X POST "/comments/package/home:okurz/python-openqa_review"