openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-01-03T10:01:46ZopenSUSE Project Management Tool
Redmine openQA Tests - action #153057 (Resolved): [tools] test fails in bootloader_start because openQA c...https://progress.opensuse.org/issues/1530572024-01-03T10:01:46ZAdaLovelace
<a name="Observation"></a>
<h2 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h2>
<p>We have got a successful build of openSUSE Tumbleweed for s390x during the Christmas time.<br>
openQA is failing in the first steps during the preparation of the bootloader and choosing the s320 console:</p>
<a name="Test-died-expected-command-exit-status-ok-got-error-at-usrlibos-autoinstconsoless3270pm-line-75-ltfhgt-line-22"></a>
<h1 >Test died: expected command exit status ok, got error at /usr/lib/os-autoinst/consoles/s3270.pm line 75, <$fh> line 22.<a href="#Test-died-expected-command-exit-status-ok-got-error-at-usrlibos-autoinstconsoless3270pm-line-75-ltfhgt-line-22" class="wiki-anchor">¶</a></h1>
<pre><code> consoles::s3270::send_3270(consoles::s3270=HASH(0x556b400f2428), "Connect(s390zl11.openqanet.opensuse.org)") called at /usr/lib/os-autoinst/consoles/s3270.pm line 315
consoles::s3270::_connect_3270(consoles::s3270=HASH(0x556b400f2428), "s390zl11.openqanet.opensuse.org") called at /usr/lib/os-autoinst/consoles/s3270.pm line 360
consoles::s3270::connect_and_login(consoles::s3270=HASH(0x556b400f2428)) called at /usr/lib/os-autoinst/consoles/s3270.pm line 424
consoles::s3270::activate(consoles::s3270=HASH(0x556b400f2428)) called at /usr/lib/os-autoinst/consoles/console.pm line 55
consoles::console::select(consoles::s3270=HASH(0x556b400f2428)) called at /usr/lib/os-autoinst/backend/baseclass.pm line 660
backend::baseclass::try {...} () called at /usr/lib/perl5/vendor_perl/5.26.1/Try/Tiny.pm line 100
eval {...} called at /usr/lib/perl5/vendor_perl/5.26.1/Try/Tiny.pm line 93
Try::Tiny::try(CODE(0x556b4000b430), Try::Tiny::Catch=REF(0x556b408595e8)) called at /usr/lib/os-autoinst/backend/baseclass.pm line 664
backend::baseclass::select_console(backend::s390x=HASH(0x556b40393d78), HASH(0x556b3fdf2ea8)) called at /usr/lib/os-autoinst/backend/baseclass.pm line 79
backend::baseclass::handle_command(backend::s390x=HASH(0x556b40393d78), HASH(0x556b4089ff50)) called at /usr/lib/os-autoinst/backend/baseclass.pm line 616
backend::baseclass::check_socket(backend::s390x=HASH(0x556b40393d78), IO::Handle=GLOB(0x556b40b26c28), 0) called at /usr/lib/os-autoinst/backend/s390x.pm line 41
backend::s390x::check_socket(backend::s390x=HASH(0x556b40393d78), IO::Handle=GLOB(0x556b40b26c28), 0) called at /usr/lib/os-autoinst/backend/baseclass.pm line 284
backend::baseclass::do_capture(backend::s390x=HASH(0x556b40393d78), undef, 1704270564.33364) called at /usr/lib/os-autoinst/backend/baseclass.pm line 311
eval {...} called at /usr/lib/os-autoinst/backend/baseclass.pm line 311
backend::baseclass::run_capture_loop(backend::s390x=HASH(0x556b40393d78)) called at /usr/lib/os-autoinst/backend/baseclass.pm line 133
backend::baseclass::run(backend::s390x=HASH(0x556b40393d78), 14, 17) called at /usr/lib/os-autoinst/backend/driver.pm line 68
backend::driver::__ANON__(Mojo::IOLoop::ReadWriteProcess=HASH(0x556b408938c8)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 329
eval {...} called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 329
Mojo::IOLoop::ReadWriteProcess::_fork(Mojo::IOLoop::ReadWriteProcess=HASH(0x556b408938c8), CODE(0x556b3f715d50)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 492
Mojo::IOLoop::ReadWriteProcess::start(Mojo::IOLoop::ReadWriteProcess=HASH(0x556b408938c8)) called at /usr/lib/os-autoinst/backend/driver.pm line 72
backend::driver::start(backend::driver=HASH(0x556b40a88648)) called at /usr/lib/os-autoinst/backend/driver.pm line 37
backend::driver::new("backend::driver", "s390x") called at /usr/lib/os-autoinst/OpenQA/Isotovideo/Backend.pm line 14
OpenQA::Isotovideo::Backend::new("OpenQA::Isotovideo::Backend") called at /usr/lib/os-autoinst/OpenQA/Isotovideo/Runner.pm line 100
OpenQA::Isotovideo::Runner::create_backend(OpenQA::Isotovideo::Runner=HASH(0x556b3b1b8a38)) called at /usr/bin/isotovideo line 134
</code></pre>
<p>openQA test in scenario opensuse-Tumbleweed-DVD-s390x-autoyast_zvm@s390x-zVM-vswitch-l2 fails in<br>
<a href="https://openqa.opensuse.org/tests/3845347/modules/bootloader_start/steps/2" class="external">bootloader_start</a></p>
<p>Has been there any openQA changes during the Christmas time, what can have an effect on the boot process for s390x?</p>
<a name="Test-suite-description"></a>
<h2 >Test suite description<a href="#Test-suite-description" class="wiki-anchor">¶</a></h2>
<p>Create HDD for s390x textmode</p>
<a name="Reproducible"></a>
<h2 >Reproducible<a href="#Reproducible" class="wiki-anchor">¶</a></h2>
<p>Fails since (at least) Build <a href="https://openqa.opensuse.org/tests/3843994" class="external">20231228</a></p>
<a name="Expected-result"></a>
<h2 >Expected result<a href="#Expected-result" class="wiki-anchor">¶</a></h2>
<p>Last good: <a href="https://openqa.opensuse.org/tests/3752152" class="external">20231115</a> (or more recent)</p>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>See related ticket <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: Support move of s390x mainframe(s) to PRG2 - o3 size:M (Resolved)" href="https://progress.opensuse.org/issues/137408">#137408</a> about the recent o3 setup</li>
<li>Confirm what s390zl11.openqanet.opensuse.org is and where it should be reachable from
<ul>
<li>Check the worker config</li>
<li>Lookup ipmi config? There is no ipmi</li>
<li>Check if there's an entry in pillars / Add a new entry</li>
</ul></li>
<li>Verify if this is a regression or a product issue</li>
<li>Optional: Try to login to the machine manually with x3270, same as openQA tests do</li>
<li>Read <a href="https://progress.opensuse.org/projects/openqav3/wiki/#o3-s390-workers" class="external">https://progress.opensuse.org/projects/openqav3/wiki/#o3-s390-workers</a> about the setup</li>
<li>Ask Oliver for details about the worker, since he might have been the last to work on it (if he still remembers), and mgriessmeier and nicksinger</li>
<li>Ask Ada</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Always latest result in this scenario: <a href="https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse&flavor=DVD&machine=s390x-zVM-vswitch-l2&test=autoyast_zvm&version=Tumbleweed" class="external">latest</a></p>
openSUSE admin - tickets #153055 (Feedback): Can not join the release team on calendar.opensuse.orghttps://progress.opensuse.org/issues/1530552024-01-03T09:48:16ZAdaLovelace
<p>I have received the following link for joining the release team on calendar.opensuse.org:<br>
<a href="https://calendar.opensuse.org/teams/release" class="external">https://calendar.opensuse.org/teams/release</a></p>
<p>I can not join the team. I am receiving the error message: "We're sorry, but something went wrong." (see screenshot)</p>
openQA Infrastructure - action #139307 (Rejected): openQA for s390x does not work at the momenthttps://progress.opensuse.org/issues/1393072023-11-12T16:17:07ZAdaLovelace
<p>Anyway openQA does not run for openSUSE Tumbleweed on s390x at the moment (after the mainframe movement to Prague).<br>
Our s390x images are succeeding (<a href="https://build.opensuse.org/project/monitor/openSUSE:Factory:zSystems?arch_local=1&defaults=0&repo_images=1&succeeded=1" class="external">https://build.opensuse.org/project/monitor/openSUSE:Factory:zSystems?arch_local=1&defaults=0&repo_images=1&succeeded=1</a> ), but openQA can not run tests for them.</p>
<p>Can you check the following, please?<br>
1) Is the network connection between openQA and the mainframe working?<br>
2) Is also the hardware, which is used for the containerized setup with running the openQA test workflow also transferred and integrated?<br>
3) Is there any openQA DNS renaming issue (I know about the change to IPv6 and other things) for our s390x setup?</p>
ZSystems - tickets #126323 (New): hashlink: 2 missing declarationshttps://progress.opensuse.org/issues/1263232023-03-21T16:13:39ZAdaLovelace
<p>hashlink is failing for s390x, because the declarations for REG_RIP and REG_RSP are missing:<br>
[ 53s] /home/abuild/rpmbuild/BUILD/hashlink-1.13/src/profile.c: In function 'get_thread_stackptr':<br>
[ 53s] /home/abuild/rpmbuild/BUILD/hashlink-1.13/src/profile.c:120:64: error: 'REG_RIP' undeclared (first use in this function)<br>
[ 53s] 120 | <em>eip = (void</em>)shared_context.context.uc_mcontext.gregs[REG_RIP];<br>
[ 53s] | <sup>~~~~~~</sup><br>
[ 53s] /home/abuild/rpmbuild/BUILD/hashlink-1.13/src/profile.c:120:64: note: each undeclared identifier is reported only once for each function it appears in<br>
[ 53s] /home/abuild/rpmbuild/BUILD/hashlink-1.13/src/profile.c:121:64: error: 'REG_RSP' undeclared (first use in this function)<br>
[ 53s] 121 | return (void*)shared_context.context.uc_mcontext.gregs[REG_RSP];<br>
[ 53s] | <sup>~~~~~~</sup><br>
[ 53s] /home/abuild/rpmbuild/BUILD/hashlink-1.13/src/profile.c:129:1: error: control reaches end of non-void function [-Werror=return-type]<br>
[ 53s] 129 | }<br>
[ 53s] | ^<br>
[ 53s] cc1: some warnings being treated as errors<br>
[ 53s] make[2]: *** [CMakeFiles/hl.dir/build.make:149: CMakeFiles/hl.dir/src/profile.c.o] Error 1<br>
[ 53s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/hashlink-1.13/build'<br>
[ 53s] make[1]: *** [CMakeFiles/Makefile2:987: CMakeFiles/hl.dir/all] Error 2</p>
<p>Link to failed build: <a href="https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/hashlink/standard/s390x" class="external">https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/hashlink/standard/s390x</a></p>
openQA Project - action #120405 (Resolved): Failed log file tests are transferred from Leap to Tu...https://progress.opensuse.org/issues/1204052022-11-14T15:09:11ZAdaLovelace
<a name="Observation"></a>
<h1 >Observation<a href="#Observation" class="wiki-anchor">¶</a></h1>
<p>Thank you for fixing the test issue for openSUSE Leap on s390x.<br>
We hve got the same issue on openSUSE Tumbleweed for s390x and with textmode now:<br>
<a href="https://openqa.opensuse.org/tests/2876172#step/logs_from_installation_system/13" class="external">https://openqa.opensuse.org/tests/2876172#step/logs_from_installation_system/13</a></p>
<p>It seems, that the test issue with failed log file uploads has been transferred with the fix for openSUSE Leap. :(</p>
<a name="Acceptance-criteria"></a>
<h1 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h1>
<ul>
<li><strong>AC1:</strong> s390 tests do not fail uploading log files</li>
</ul>
<a name="Suggestions"></a>
<h1 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h1>
<ul>
<li>Verify that previous fix has been deployed to all O3 workers (be aware that s390 tests run in containers)</li>
<li>Have a look at <a href="https://progress.opensuse.org/projects/openqav3/wiki/#o3-s390-workers" class="external">https://progress.opensuse.org/projects/openqav3/wiki/#o3-s390-workers</a> for how the s390x worker setup is configured (on o3)</li>
</ul>
openQA Project - action #119713 (Resolved): Leap tests are failing because of failed log file upl...https://progress.opensuse.org/issues/1197132022-11-01T14:10:23ZAdaLovelace
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>openQA tests are failing for openSUSE Leap 15.5 on s390x. The curiosity is, that log files can not be uploaded in multiple tests.<br>
<a href="https://openqa.opensuse.org/tests/2842380#step/logs_from_installation_system/13" class="external">https://openqa.opensuse.org/tests/2842380#step/logs_from_installation_system/13</a></p>
<p>textinfo is affected with textinfo-logs.tar.bz2.<br>
logs_from_installation_system is affected with y2logs.tar.bz2.</p>
<p>the test tries to reach 192.168.112.6:21013. IPv4 which might not work as the IPv4 address is from openqaworker1 but the openQA worker instance runs within a container. But <a href="https://openqa.opensuse.org/tests/2833511#step/logs_from_installation_system/12" class="external">https://openqa.opensuse.org/tests/2833511#step/logs_from_installation_system/12</a> on Tumbleweed seems to work from 2022-10-25, maybe broke after that?</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The scenario <a href="https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse&flavor=DVD&machine=s390x-zVM-vswitch-l2&test=textmode&version=15.5" class="external">https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse&flavor=DVD&machine=s390x-zVM-vswitch-l2&test=textmode&version=15.5</a> passes again</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Investigate the difference between the mentioned bad and <a href="https://openqa.opensuse.org/tests/2833511#step/logs_from_installation_system/12" class="external">https://openqa.opensuse.org/tests/2833511#step/logs_from_installation_system/12</a> on Tumbleweed which still works fine</li>
<li>Look into related issues for background stories</li>
</ul>
openQA Project - action #119077 (Resolved): openQA infrastructure issues for s390x and PowerPChttps://progress.opensuse.org/issues/1190772022-10-19T12:26:48ZAdaLovelace
<p>Anyway, the tests in openQA are scheduled for s390x and PowerPC for over 10 hours (Tumbleweed and Leap) every day.<br>
It seems, that the tests can not be started. Are any network issues available?</p>
<p>The tests for s390x (Tumbleweed) have been scheduled over 10 hours yesterday. They will be skipped for the next release then.<br>
Can you take a look on this openQA issue (infrastructure related), please?</p>
ZSystems - tickets #116215 (Resolved): Update python-epubmergehttps://progress.opensuse.org/issues/1162152022-09-02T18:58:35ZAdaLovelace
<p>The package python-epubmerge should be updated.</p>
<p>1) Branch <a href="https://build.opensuse.org/package/show/devel:languages:python/python-epubmerge" class="external">https://build.opensuse.org/package/show/devel:languages:python/python-epubmerge</a><br>
2) "osc co" of your home directory<br>
3) Download the latest tar.gz from <a href="https://github.com/JimmXinu/EpubMerge/releases" class="external">https://github.com/JimmXinu/EpubMerge/releases</a><br>
4) "osc rm v2.9.0.tar.gz"<br>
5) "osc add" for the new tar archive<br>
6) Replace the version number in the file python-epubmerge.spec<br>
7) "osc commit"</p>
ZSystems - tickets #116212 (New): Add files to package config of python-celerymonhttps://progress.opensuse.org/issues/1162122022-09-02T18:52:34ZAdaLovelace
<p>The package python-celerymon is failing because a list of files is installed, but not packaged:<br>
<a href="https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/python-celerymon/standard/s390x" class="external">https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/python-celerymon/standard/s390x</a><br>
That means, that they are not referenced in the spec file.</p>
<p>1) Branch <a href="https://build.opensuse.org/package/show/devel:languages:python/python-celerymon" class="external">https://build.opensuse.org/package/show/devel:languages:python/python-celerymon</a><br>
2) "osc co" of your home directory<br>
3) Open python-celerymon.spec<br>
4) Go down to the files section<br>
5) Compare the files structure with the referenced files in the error log<br>
6) Create an additional line matching the requirements of the listed files<br>
7) "osc commit"</p>
ZSystems - tickets #116209 (New): Expand memory for package python-websocketshttps://progress.opensuse.org/issues/1162092022-09-02T18:41:01ZAdaLovelace
<p>The package python-websockets is failing because of timeouts and the build is too slow:<br>
<a href="https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/python-websockets/standard/s390x" class="external">https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/python-websockets/standard/s390x</a></p>
<p>That can be fixed with a constraints file, that a build host with more memory should be chosen for this package.<br>
1) Branch <a href="https://build.opensuse.org/package/show/devel:languages:python/python-websockets" class="external">https://build.opensuse.org/package/show/devel:languages:python/python-websockets</a><br>
2) "osc co" of your home directory<br>
3) Create a file with the name _constraints<br>
4) Learn with this example, which configurations are possible and how:<br>
<a href="https://build.opensuse.org/package/view_file/mozilla:Factory/MozillaFirefox/_constraints?expand=1" class="external">https://build.opensuse.org/package/view_file/mozilla:Factory/MozillaFirefox/_constraints?expand=1</a><br>
5) Create a minimal configuration for the architecture s390x as an "overwrite condition" with expanding the physicalmemory.<br>
6) "osc add _constraints"<br>
7) "osc commit"</p>
ZSystems - tickets #116206 (Resolved): Syntax error in python-webassetshttps://progress.opensuse.org/issues/1162062022-09-02T18:31:08ZAdaLovelace
<p>The build for python-webassets is failing because of a syntax error:<br>
[ 28s] self = <br>
[ 28s] <br>
[ 28s] def test_cssutils(self):<br>
[ 28s] > cssutils = pytest.importorskip('cssutils')<br>
[ 28s] E File "/usr/lib/python3.8/site-packages/cssutils/<strong>init</strong>.py", line 330<br>
[ 28s] E except xml.dom.HierarchyRequestErr, e:<br>
[ 28s] E ^<br>
[ 28s] E SyntaxError: invalid syntax<br>
[ 28s] </p>
<p><a href="https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/python-webassets/standard/s390x" class="external">https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/python-webassets/standard/s390x</a></p>
<p>1) Branch <a href="https://build.opensuse.org/package/show/devel:languages:python/python-webassets" class="external">https://build.opensuse.org/package/show/devel:languages:python/python-webassets</a><br>
2) "osc co" of your home directory<br>
3) Identify in the error message above, what is wrong in this Python syntax.<br>
4) Create a patch file (Mentors are supporting)<br>
5) "osc add" on the patch file<br>
6) "osc commit"</p>
ZSystems - tickets #116203 (Resolved): Update python-pytest-subtesthackhttps://progress.opensuse.org/issues/1162032022-09-02T18:02:27ZAdaLovelace
<p>Some tests are failing for s390x within the package python-pytest-subtesthack.<br>
We want to fix the problem with an update.</p>
<p>1) Branch <a href="https://build.opensuse.org/package/show/devel:languages:python:pytest/python-pytest-subtesthack" class="external">https://build.opensuse.org/package/show/devel:languages:python:pytest/python-pytest-subtesthack</a><br>
2) "osc co" of your home directory<br>
3) "osc rm 0.1.2.tar.gz"<br>
4) Download latest tar.gz from <a href="https://github.com/untitaker/pytest-subtesthack/tags" class="external">https://github.com/untitaker/pytest-subtesthack/tags</a><br>
5) "osc add 0.2.0.tar.gz"<br>
6) Modify python-pytest-subtesthack.spec with the new version number<br>
7) "osc commit"</p>
ZSystems - tickets #116200 (New): Improve performance of the build host of package python-svgwritehttps://progress.opensuse.org/issues/1162002022-09-02T17:48:25ZAdaLovelace
<p>python-svgwrite is failing with the test TestPathDataParser.test_performance:<br>
[ 214s] self = <br>
[ 214s] <br>
[ 214s] def test_performance(self):<br>
[ 214s] start = time.time()<br>
...<br>
[ 214s] > self.assertLess(time.time()-start, 0.1, "Parsing path string is too slow")<br>
[ 214s] E AssertionError: 0.1109471321105957 not less than 0.1 : Parsing path string is too slow<br>
[ 214s] <br>
[ 214s] tests/test_pathdataparser.py:146: AssertionError<br>
<a href="https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/python-svgwrite/standard/s390x" class="external">https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/python-svgwrite/standard/s390x</a></p>
<p>We want to try to fix this issue with a selection of a build host with more CPU for the architecture s390x.</p>
<p>1) Branch <a href="https://build.opensuse.org/package/show/devel:languages:python/python-svgwrite" class="external">https://build.opensuse.org/package/show/devel:languages:python/python-svgwrite</a><br>
2) "osc co" of your home directory<br>
3) Create a file with the name _constraints<br>
4) Try to understand host configurations with this constraints file: <a href="https://build.opensuse.org/package/view_file/mozilla:Factory/MozillaFirefox/_constraints?expand=1" class="external">https://build.opensuse.org/package/view_file/mozilla:Factory/MozillaFirefox/_constraints?expand=1</a><br>
5) Write your own constraints file with an overwrite condition for s390x and more CPU<br>
6) Ask the Representatives for help, if needed<br>
7) "osc add _constraints"<br>
8) osc commit</p>
ZSystems - tickets #116197 (Resolved): wrong version numbers in package mumps:serialhttps://progress.opensuse.org/issues/1161972022-09-02T17:21:35ZAdaLovelace
<p>mumps:serial is failing because of wrong version numbers.<br>
<a href="https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/mumps:serial/standard/s390x" class="external">https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/mumps:serial/standard/s390x</a></p>
<p>There is following error message:<br>
[ 720s] libmumps5.s390x: E: shlib-policy-name-error (Badness: 10000) SONAME: libcmumps_seq.so.5.3.5 (/usr/lib64/libcmumps_seq.so.5.3.5), expected package suffix: 5_3_5<br>
[ 720s] libmumps5.s390x: E: shlib-policy-name-error (Badness: 10000) SONAME: libdmumps_seq.so.5.3.5 (/usr/lib64/libdmumps_seq.so.5.3.5), expected package suffix: 5_3_5<br>
[ 720s] libmumps5.s390x: E: shlib-policy-name-error (Badness: 10000) SONAME: libmpiseq_seq.so.5.3.5 (/usr/lib64/libmpiseq_seq.so.5.3.5), expected package suffix: 5_3_5<br>
[ 720s] libmumps5.s390x: E: shlib-policy-name-error (Badness: 10000) SONAME: libmumps_common.so.5.3.5 (/usr/lib64/libmumps_common_seq.so.5.3.5), expected package suffix: 5_3_5<br>
[ 720s] libmumps5.s390x: E: shlib-policy-name-error (Badness: 10000) SONAME: libpord_seq.so.5.3.5 (/usr/lib64/libpord_seq.so.5.3.5), expected package suffix: 5_3_5<br>
[ 720s] libmumps5.s390x: E: shlib-policy-name-error (Badness: 10000) SONAME: libsmumps_seq.so.5.3.5 (/usr/lib64/libsmumps_seq.so.5.3.5), expected package suffix: 5_3_5<br>
[ 720s] libmumps5.s390x: E: shlib-policy-name-error (Badness: 10000) SONAME: libzmumps_seq.so.5.3.5 (/usr/lib64/libzmumps_seq.so.5.3.5), expected package suffix: 5_3_5<br>
[ 720s] The package contains shared library but is not named after its SONAME.</p>
<p>1) Branch <a href="https://build.opensuse.org/package/show/science/mumps" class="external">https://build.opensuse.org/package/show/science/mumps</a><br>
2) "osc co" of your home directory<br>
3) open mumps.spec<br>
4) Search for "libcmumps_seq" and the other listed files<br>
5) Identify, how the version numbers are created<br>
6) Adopt the version number to 5_3_5<br>
7) "osc commit"</p>
ZSystems - tickets #116194 (New): libgsasl: use of possibly-NULL '*output' where non-null expectedhttps://progress.opensuse.org/issues/1161942022-09-02T14:14:54ZAdaLovelace
<p>That is a s390x specific bugfix for the package libgsasl.<br>
[ 316s] client.c: In function '<u>gsasl_login_client_step':<br>
[ 316s] client.c:88:21: error: use of possibly-NULL '*output' where non-null expected [CWE-690] [-Werror=analyzer-possible-null-argument]<br>
[ 316s] 88 | *output_len = strlen (*output);<br>
[ 316s] | <sup>~~~~~~~~~~~~~~~</sup><br>
[ 316s] '_gsasl_login_client_step': events 1-6<br>
[ 316s] |<br>
[ 316s] | 68 | switch (state->step)<br>
[ 316s] | | <sup>~~~~~</sup><br>
[ 316s] | | |<br>
[ 316s] | | (1) following 'case 1:' branch...<br>
[ 316s] |......<br>
[ 316s] | 82 | case 1:<br>
[ 316s] | | ~~~~<br>
[ 316s] | | |<br>
[ 316s] | | (2) ...to here<br>
[ 316s] | 83 | p = gsasl_property_get (sctx, GSASL_PASSWORD);<br>
[ 316s] | 84 | if (!p)<br>
[ 316s] | | ~<br>
[ 316s] | | |<br>
[ 316s] | | (3) following 'false' branch (when 'p' is non-NULL)...<br>
[ 316s] |......<br>
[ 316s] | 87 | *output = strdup (p);<br>
[ 316s] | | ~ ~~~~~~~~~~<br>
[ 316s] | | | |<br>
[ 316s] | | | (5) this call could return NULL<br>
[ 316s] | | (4) ...to here<br>
[ 316s] | 88 | *output_len = strlen (*output);<br>
[ 316s] | | ~~~~~~~~~~~~~~~~<br>
[ 316s] | | |<br>
[ 316s] | | (6) argument 1 ('strdup(p)') from (5) could be NULL where non-null expected<br>
[ 316s] |<br>
[ 316s] In file included from ./../gl/string.h:41,<br>
[ 316s] from client.c:31:<br>
[ 316s] /usr/include/string.h:407:15: note: argument 1 of 'strlen' must be non-null<br>
[ 316s] 407 | extern size_t strlen (const char *</u>_s)<br>
[ 316s] | <sup>~~~~~</sup><br>
[ 316s] cc1: all warnings being treated as errors<br>
[ 316s] make[2]: *** [Makefile:1561: client.lo] Error 1</p>
<p>log: <a href="https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/libgsasl/standard/s390x">https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems/libgsasl/standard/s390x</a></p>
<p>1) Branch <a href="https://build.opensuse.org/package/show/devel:libraries:c_c++/libgsasl">https://build.opensuse.org/package/show/devel:libraries:c_c++/libgsasl</a><br>
2) "osc co" of your home directory<br>
3) Create patch for fixing the non-null error<br>
4) Build it on the mainframe<br>
5) "osc add" of the patch<br>
6) "osc commit"</p>