[opensuse-factory] New Tumbleweed snapshot 20161031 released!
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&version=Tumbleweed&build=20161031 When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem. Packages changed: apparmor calligra dbus-1-glib gstreamer-transcoder inn kiwi (7.04.6 -> 7.04.8) libqt5-qtwebengine libwps llvm3_8 virt-viewer yast2-network (3.2.7 -> 3.2.8) === Details === ==== apparmor ==== Subpackages: apparmor-abstractions apparmor-docs apparmor-parser apparmor-profiles apparmor-utils libapparmor-devel libapparmor1 libapparmor1-32bit pam_apparmor pam_apparmor-32bit perl-apparmor python3-apparmor - add nscd-var-lib.diff to allow /var/lib/nscd/ in the nscd profile and abstractions/nameservice (path changed in latest nscd in Tumbleweed) ==== calligra ==== Subpackages: calligra-extras-dolphin calligra-extras-okular calligra-stage calligra-words-common - Disable Vc-devel-static build requirement again, it currently makes calligra crash on runtime, and Vc 1.3.0 is entering TW soon anyway which will break calligra's build ==== dbus-1-glib ==== Subpackages: dbus-1-glib-32bit dbus-1-glib-devel - Split out dbus-binding-tool in own sub-package. ==== gstreamer-transcoder ==== Subpackages: libgsttranscoder-1_0-0 typelib-1_0-GstTranscoder-1_0 - Update descriptions ==== inn ==== - Fix tmpfiles.d usage to give it at least a chance to work ==== kiwi ==== Version update (7.04.6 -> 7.04.8) Subpackages: kiwi-desc-isoboot kiwi-desc-netboot kiwi-desc-oemboot kiwi-desc-vmxboot kiwi-doc kiwi-media-requires kiwi-pxeboot kiwi-templates kiwi-tools - v7.04.8 released - Only one changelog section is allowed - Make sure an empty %changelog tag exists - No longer write a %changelog section in the spec For some reason the packaging concept no longer needs a changelog section in the spec file. Most likely the build service scripts now generates those information from the .changes file which lead to duplicate changelog information in the package - v7.04.7 released - Fixed a rounding error in partedMBToCylinder(): bc truncates number of cylinders to zero decimal places, which results in a partition that is slightly smaller than the requested size. Add one cylinder to compensate. - drop kiwi-instsource-plugins It got moved to https://github.com/openSUSE/kiwi-instsource-plugins ==== libqt5-qtwebengine ==== - Add disable-gpu-when-using-nouveau-boo-1005323.diff. Disables the use of the gpu by webengine when the nouveau opengl driver is detected since nouveau doesn't support rendering from different threads. Also, allows to use two environment variables QT_WEBENGINE_DISABLE_GPU to force the disabling of the gpu and QT_WEBENGINE_DISABLE_NOUVEAU_WORKAROUND to disable the detection of nouveau, just in case someone wants to try with newer nouveau releases (boo#1005323, boo#997171). ==== libwps ==== - Remove redundant pkgconfig requires ==== llvm3_8 ==== Subpackages: libLLVM3_8 libLLVM3_8-32bit - Install FileCheck utility, needed by rust bsc#1006199 ==== virt-viewer ==== - remove exclusivearch ==== yast2-network ==== Version update (3.2.7 -> 3.2.8) - Fixed a hardcoded interface name in a CLI test (bsc#1006799) - 3.2.8 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Tue, 2016-11-01 at 16:56 +0100, Dominique Leuenberger wrote:
Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1& version=Tumbleweed&build=20161031
Hi Dim*, I understand the "soft failure" vs. "failure" nature of OpenQA, but can you (or can you ask someone to ;-) explain the policy on allowing Tumbleweed builds with failed tests? I'm just looking for some clarity on why we allow some failures, and how decisions are made to ship with known failures. - -- James Mason Technical Architect, Public Cloud openSUSE Member SUSE jmason@suse.com -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJYGL0oAAoJEBs5UYhsRJAj6F4IAKhMobjzPhwb8T21m/Whe7k4 itxfC3qOmJeoFPf/wp29bGQ29EgRIVSEVc7XTFAdfKfINLgWI5YqathHvbL2q7At QU7ZSPwfs/Vg4vSACcmKc+apMOP+1RSPEbq+sKnyBW5kFZZmyR1XVDFOSOcS5GtS tPsKJQbLycayxg9czmRDd2m6URaBXnWOhfX8DIfJjzaVo29gC42cUqCLoaI3Fm4n HyAHM8npYbd7lNQviWxZYe/19U5Mtm5bKXQPTfhj+qZMJOECu2BA4yiMojXwa9Fj ug6LYsAx7hk3CrCfuFy+QJHjwFAV2gxjVAa9WkdGpoqhvx0VlaBIXdl2hOTjbrM= =amd2 -----END PGP SIGNATURE-----
On Tue, 2016-11-01 at 16:04 +0000, James Mason wrote:
On Tue, 2016-11-01 at 16:56 +0100, Dominique Leuenberger wrote:
Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid= 1&; version=Tumbleweed&build=20161031
Hi Dim*,
I understand the "soft failure" vs. "failure" nature of OpenQA, but can you (or can you ask someone to ;-) explain the policy on allowing Tumbleweed builds with failed tests?
I'm just looking for some clarity on why we allow some failures, and how decisions are made to ship with known failures.
Hi James, Let me try to explain, with pointing to some sample test from the last run: * Soft fails are never a reason for a blocked snapshot * 'unit fails' inside a test, unless it is marked important, results in the test suite to 'succeed' (status passed) https://openqa.opensuse.org/tests/295125#step/multi_users_dm/11 => multi_users_dm test is 'failed' - overall test suite is 'softfailed' (multi_users_dm is not marked important) Taking only this into account, snapshot 1031 passed with: Passed: 62 / Soft Failre: 33 / Failed: 11 As explained above, Soft Failures are considered 'passed' - but need some investigation (some are long standing bugs in the tests, quite a few just 'random' failures which are being worked out) Which leaves us with the more interesting case of the '11 failed' (after all, the snapshot had been released) For this we maintain a list of 'known failures' - so tests that are currently broken, due to various issues. If you check the overview page for the snapshot you will see that we try to tag known failures with bug references - making it much easier to track them. Finally, it is my responsibility to investigate on new 'failed' and decide if this is still sensible to let the snapshot pass or if it's required to block it now. The basic rule there is: unless the reason is understood, I'm not adding a failure to the list of known_failures. The overview of current failures can be found at: https://openqa.opensuse.org/tests/overview?distri=opensuse&version=Tumb leweed&build=20161031&groupid=1 Simply filter on 'failed' tests and see the 11 failed; 9 pf them have a bug reference (or progress item) assigned. 2 of the tests (42.1 Updates) 'changed' the reason they failed between the last run and this run and those are the ones without bug assigned, and the thing i am currently looking in to. Does that help? Cheers, Dominique
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Tue, 2016-11-01 at 17:26 +0100, Dominique Leuenberger / DimStar wrote:
Does that help?
Yes, makes perfect sense. Thank you! If I could suggest one change, consider adding this to the wiki, with links to the (helpful) openQA reports. - -- James Mason <jmason@suse.com> SUSE -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJYGMPRAAoJEBs5UYhsRJAj9KcH/0cl3IMYU+RBxGBelaTPPzUM 2cl8WInodrgdyKORgAucw66J94DibQ+dH64Q8c9H95l6cb0DscuycqpxZJMKszsI tSMkXg0oblag7N6/tqWS/MSbdUyf956sB4kcR9CO+fUPWH+C8WGLLbUKGxZzzaI6 UuFuIapFxSYfSfJd7AlslV73uiBpMg4T9veeYS/XDV2VCO1OQhAzsA11gL0Rr9aw ok14KodEQ0SKHdPQcu4Erll+AONkmHVh44NBIedoRssH5Yg+k2a9vmTXJcCo2JXs x7RO0nqBUwEB6tUep3klBwxnLnbMQdL+QolbU4XFN94py/YiC9TbviItauLnW1s= =Qnrm -----END PGP SIGNATURE-----
participants (3)
-
Dominique Leuenberger -
Dominique Leuenberger / DimStar -
James Mason